Improve troubleshooting links in FRITZ!Tools

[mib1185]

Proposed change

This points to the generell troubleshooting tips for debug logging and downloading the diagnostics data.

Type of change

• Spelling, grammar or other readability improvements (current branch).
• Adjusted missing or incorrect information in the current documentation (current branch).
• Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • I've opened up a PR to add logos and icons in Brands repository.
• Added documentation for a new feature I'm adding to Home Assistant (next branch).
• Removed stale or deprecated documentation.

Additional information

• Link to parent pull request in the codebase:
• Link to parent pull request in the Brands repository:
• This PR fixes or closes issue: fixes #

Checklist

• This PR uses the correct branch, based on one of the following:
  • I made a change to the existing documentation and used the current branch.
  • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
• The documentation follows the Home Assistant documentation standards.

[netlify]

✅ Deploy Preview for home-assistant-docs ready!

Name	Link
🔨 Latest commit	9416811
🔍 Latest deploy log	https://app.netlify.com/projects/home-assistant-docs/deploys/693556e6d1e8b300085397e7
😎 Deploy Preview	https://deploy-preview-42367--home-assistant-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull request overview

This PR updates the troubleshooting section links in the FRITZ!Tools integration documentation to point to more specific anchor links in the troubleshooting guide. While the new links are technically valid, the change deviates from established documentation patterns used across most other integration files and removes the use of a glossary term reference.

Key changes

• Updated debug logging link from #debug-logs-and-diagnostics to #enabling-debug-logging
• Replaced glossary term {% term diagnostics %} with a regular link to #download-diagnostics

[Copilot]

The change removes the use of the glossary term {% term diagnostics %} and replaces it with a regular link [diagnostics data](/docs/configuration/troubleshooting/#download-diagnostics). According to the documentation guidelines, glossary term references should be used when appropriate as they provide tooltips with term definitions for better user experience.

Additionally, most other integration files use a more common pattern:

• For debug logging: /docs/configuration/troubleshooting/#debug-logs-and-diagnostics
• For diagnostics: either [diagnostics](/integrations/diagnostics) or {% term diagnostics %}

Consider using one of these established patterns for consistency with the rest of the documentation. For example:

In any case, when reporting an issue, please enable [debug logging](/docs/configuration/troubleshooting/#debug-logs-and-diagnostics), restart the integration, and as soon as the issue re-occurs stop the debug logging again (_download of debug log file will start automatically_). Further _if still possible_, please also download the {% term diagnostics %} data. If you have collected the debug log and the diagnostics data, provide them with the issue report.

[c0ffeeca7]

Nice! Thank you, @mib1185 👍