Fix two anchors (#633)

Staudey · web-flow · commit d7f5b630725c · 2025-06-07T18:06:19.000-04:00
Signed-off-by: Thomas Staudinger &lt;Staudi.Kaos@gmail.com&gt;
diff --git a/docs/packaging/appstream-metainfo.md b/docs/packaging/appstream-metainfo.md
@@ -30,7 +30,7 @@ There are a few scenarios that Packagers might encounter:
 | 1   | An application already provides appstream metainfo                                               | Nothing to do                                                                                                                                                                                                                |
 | 2   | An application contains appstream metainfo in the source package but we do not install it        | Install the appstream metainfo to `/usr/share/metainfo`. _Example_: [here](https://github.com/getsolus/packages/commit/0a726a53454e7c8a6b0e66de69d59bcc66f0fc19)                                                             |
 | 3   | An application doesn't contain appstream metainfo in the source package but it exists on Flathub | Borrow and tweak the appstream metainfo from the Flathub repo. Encourage upstream project to add it to their source. _Example_: [here](https://github.com/getsolus/packages/commit/da2f65b93f412da43d1db9edbcb08bb90517a0eb) |
-| 4   | An application doesn't provide appstream metainfo and it doesn't exist on flathub                | See [here](writing-appstream-metainfo). _Example_: [here](https://github.com/getsolus/packages/commit/414219d8b2ceeabe85178d3a467f81b9131016f4)                                                         |
+| 4   | An application doesn't provide appstream metainfo and it doesn't exist on flathub                | See [here](#writing-appstream-metainfo). _Example_: [here](https://github.com/getsolus/packages/commit/414219d8b2ceeabe85178d3a467f81b9131016f4)                                                         |
 | 5   | Appstream metainfo is provided but composition of it is failing                                   | See [here](#testing-appstream-metainfo). _Example_: [here](https://github.com/getsolus/packages/commit/583b7c742caf50e2f66a70e9b62e9b91566c03f5).                                    |
 
 AppStream metainfo is to be installed in the `/usr/share/metainfo/` directory. It must be placed in the package which should be installed in order to get the software described by the respective metadata. This means that you might need to move the _.metainfo.xml or _.appdata.xml to the right (sub)package.
diff --git a/docs/user/troubleshooting/installation.md b/docs/user/troubleshooting/installation.md
@@ -23,4 +23,4 @@ Legacy installations on Solus use the GRUB boot loader on an MBR disk. Only one
 
 ### EFI
 
-EFI allows for multiple boot loaders to be installed, which means you can boot the Solus boot loader directly. To ensure you are booting Solus you need to boot `Linux Boot Manager` from the EFI options. Common keys for bringing up a boot menu or the options during boot are hitting `Esc/F2/F9/F10/F11/F12` during boot (this differs per motherboard). If a boot loader for another OS is not listed in the menu, then it is not correctly registered (and therefore not installed correctly). You can make the Solus boot menu appear via [Displaying the Solus boot menu on boot](/docs/user/quick-start/boot-management#displaying-the-boot-menu-by-default-every-boot) which should be able to boot Windows (as it's registered with UEFI properly) as well as Solus, but not other systems.
+EFI allows for multiple boot loaders to be installed, which means you can boot the Solus boot loader directly. To ensure you are booting Solus you need to boot `Linux Boot Manager` from the EFI options. Common keys for bringing up a boot menu or the options during boot are hitting `Esc/F2/F9/F10/F11/F12` during boot (this differs per motherboard). If a boot loader for another OS is not listed in the menu, then it is not correctly registered (and therefore not installed correctly). You can make the Solus boot menu appear via [Displaying the Solus boot menu on boot](/docs/user/quick-start/boot-management#display-the-boot-menu-by-default) which should be able to boot Windows (as it's registered with UEFI properly) as well as Solus, but not other systems.

Original file line number	Diff line number	Diff line change
`@@ -23,4 +23,4 @@ Legacy installations on Solus use the GRUB boot loader on an MBR disk. Only one`
`23`	`23`
`24`	`24`	`### EFI`
`25`	`25`
`26`		-EFI allows for multiple boot loaders to be installed, which means you can boot the Solus boot loader directly. To ensure you are booting Solus you need to boot `Linux Boot Manager` from the EFI options. Common keys for bringing up a boot menu or the options during boot are hitting `Esc/F2/F9/F10/F11/F12` during boot (this differs per motherboard). If a boot loader for another OS is not listed in the menu, then it is not correctly registered (and therefore not installed correctly). You can make the Solus boot menu appear via [Displaying the Solus boot menu on boot](/docs/user/quick-start/boot-management#displaying-the-boot-menu-by-default-every-boot) which should be able to boot Windows (as it's registered with UEFI properly) as well as Solus, but not other systems.
	`26`	+EFI allows for multiple boot loaders to be installed, which means you can boot the Solus boot loader directly. To ensure you are booting Solus you need to boot `Linux Boot Manager` from the EFI options. Common keys for bringing up a boot menu or the options during boot are hitting `Esc/F2/F9/F10/F11/F12` during boot (this differs per motherboard). If a boot loader for another OS is not listed in the menu, then it is not correctly registered (and therefore not installed correctly). You can make the Solus boot menu appear via [Displaying the Solus boot menu on boot](/docs/user/quick-start/boot-management#display-the-boot-menu-by-default) which should be able to boot Windows (as it's registered with UEFI properly) as well as Solus, but not other systems.