Fix internal 404 links, wrong anchors, and mkdocs build warning (#376)

* Fix invalid internal relative links that led to 404 pages

* Fix links to invalid anchors

* Mkdocs nav config: link directly to Music Providers page instead of subsection

... in order to avoid mkdocs warning at build time

Author: Horgix

docs/audiopipeline.md

@@ -27,7 +27,7 @@ The maximum sample rate that can be expected can be found in the [Player Provide
 ## Digital Signal Processing
 ![image](assets/screenshots/audiopipeline-dsp.png){ width=500 }
 
-In this example [DSP](player-support/index.md/#dsp-settings) has been enabled. High level information about the DSP filters which have been applied are shown. A tooltip is available to explain why the DSP is not supported if that is the case (See the example below in [Groups](#groups)).
+In this example [DSP](settings/individual-player.md/#dsp-settings) has been enabled. High level information about the DSP filters which have been applied are shown. A tooltip is available to explain why the DSP is not supported if that is the case (See the example below in [Groups](#groups)).
 
 Also of note in this example is the icon shown in the input section where the codec icon is normally. This icon will be displayed when MA cannot determine the codec and can occur with container formats such as [wavpack](https://www.wavpack.com/), [m4a](https://cloudinary.com/guides/video-formats/what-is-the-m4a-format-understanding-the-difference-between-m4a-mp3-and-wav) or [DSD64](https://en.wikipedia.org/wiki/Direct_Stream_Digital).
 

docs/faq/groups.md

@@ -10,7 +10,7 @@ description: Player Grouping Functionality in Music Assistant
 
 Music Assistant uses four types of groups (these are outlined in the [Grouping Players](../ui.md#grouping-players) section and three of the types are described in detail below) which provides a flexible way to combine players together. When a group is powered on then playback to individual members of the group is no longer possible. To play to an individual member, the group must be powered off or the individal player must be removed from the group. If the group is still powered on then players can only be removed from [Temporary Sync Groups](#temporary-sync-group), or from [Sync Groups](#sync-groups) and [Universal Groups](#universal-groups) which have the dynamic member option enabled. When allowable, players can be removed by using the checkboxes in the [Player List](../ui.md#player-list) or by using the [HA media_player.unjoin action](https://www.home-assistant.io/integrations/media_player/#media-control-actions).
 
-See also the section on Announcements [Group Behaviour](../integration/announcements/#group-behaviour).
+See also the section on Announcements [Group Behaviour](../integration/announcements.md/#group-behaviour).
 
 ## Temporary Sync Group
 

docs/faq/troubleshooting.md

@@ -110,7 +110,7 @@ For the iOS app see [here](https://community.home-assistant.io/t/anyone-know-how
 
 MA is an INPUT to your amplifier. So you need to power on your amplifier and then select the INPUT that MA is streaming to (e.g. AirPlay, DLNA, Chromecast). For this reason MA does not see the amplifier zones it only sees the compatible inputs of the amplifier. 
 
-Some amplifiers may auto turn on when a signal is detected so check the amplifier options. If this functionality is not available then you will need to power on the amplifier via another means which could be by [assigning a HA entity to the player control](../player-support/index.md#player-controls). 
+Some amplifiers may auto turn on when a signal is detected so check the amplifier options. If this functionality is not available then you will need to power on the amplifier via another means which could be by [assigning a HA entity to the player control](../settings/individual-player.md/#player-controls). 
 
 # My local music isn’t being imported or I’m seeing missing ID3 tag warnings in the logs
 

docs/music-providers/apple-music.md

@@ -16,7 +16,7 @@ Music Assistant has support for [Apple Music](https://music.apple.com/)! Contrib
 | [Recommendations](../ui.md#view-home) Supported | No |
 | Lyrics Supported | No |
 | [Radio Mode](../ui.md#track-menu) | Yes |
-| Maximum Stream Quality | [Lossy AAC (256kbps)](#known-issues--notes) |
+| Maximum Stream Quality | [Lossy AAC (256kbps)](#known-issues-notes) |
 | Login Method | Cookie |
 
 ### Other

docs/music-providers/builtin.md

@@ -1,6 +1,6 @@
 # Builtin Provider  ![Preview image](../assets/icon.png){ width=70 align=right }
 
-The Builtin provider supports manually adding track and radio station URLs to the database and it also generates various [Playlists](../usage/#playlists).
+The Builtin provider supports manually adding track and radio station URLs to the database and it also generates various [Playlists](../usage.md/#playlists).
 
 ## Features
 

docs/player-support/squeezelite.md

@@ -9,7 +9,7 @@ Squeezelite clients are available for, and can run on, almost any hardware from
 ## Features
 
 - Squeezelite client devices are automatically detected by Music Assistant
-- Individual player [DSP settings](index.md/#dsp-settings) will be used for [group](../faq/groups.md) playback
+- Individual player [DSP settings](../settings/individual-player.md/#dsp-settings) will be used for [group](../faq/groups.md) playback
 - Squeezelite client device buttons support
   - Any physical control buttons on the device should be supported as long as [flow mode](../faq/tech-info.md/#track-queueing) is not enabled
 

docs/settings/individual-player.md

@@ -66,7 +66,7 @@ There are a number of configurable options for controlling the volume of announc
 
 Each player has a number of options available to control the behaviour of the power, volume and mute controls in the MA UI. By default, if a device supports these controls then that native behaviour will be used or if the control is not supported then it will be disabled in the UI (the setting will indicate NONE). It is also possible to manually disable the controls by changing the setting to NONE.
 
-It is possible to map other HA entities to the MA player controls. in order for this to be an option the HA entities need to be first exposed to MA via the settings in the [HA Plugin](../ha-plugin.md/#configuring-the-home-assistant-plugin).
+It is possible to map other HA entities to the MA player controls. in order for this to be an option the HA entities need to be first exposed to MA via the settings in the [HA Plugin](../ha-plugin.md).
 
 **Power** If a player does not support power but it is desired that the player has an on and off state then a FAKE option is available which will simulate the on/off functionality. 
 

docs/ui.md

@@ -40,7 +40,7 @@ This view will change depending on screen width. With wider displays you will be
 
 The [Audio Pipeline](audiopipeline.md) selectable label is described above in the [Player Bar](#player-bar) section.
 
-You can also access the [Now Playing view directly via URL](faq/how-to.md/#access-the-now-playing-view-directly-via-url)
+You can also access the [Now Playing view directly via URL](faq/how-to.md/#now-playing-view)
 
 When the favourite icon is solid then selecting that will bring up two options - `Remove from Favorites` and `Add to Playlist`. It is possible that if the favorite status is changed from a different view after playback has commenced then the favourite status may not indicate correctly until playback of the track is restarted.
 ***************************************************************

mkdocs.yml

@@ -11,7 +11,7 @@ nav:
       - Core Settings: settings/core.md
       - Player Provider Settings: settings/player-provider.md
       - Individual Player Settings: settings/individual-player.md
-      - Music Provider Settings: music-providers/#settings
+      - Music Provider Settings: music-providers/index.md
   - Home Assistant Integration:
       - integration/index.md
       - Installation: integration/installation.md