Fix links

Don't use footnote-style links. I think the slugs are getting confused by the MD parser with others elsewhere in the docs.

Author: timdorr

docs/upgrading/v5.md

@@ -7,7 +7,7 @@ order: 1
 
 ## Backwards Compatibility Package
 
-Instead of upgrading and updating all of your code at once (which is incredibly difficult and prone to bugs), the backwards compatibility package enables you to upgrade one component, one hook, and one route at a time by running both v5 and v6 in parallel. Any code you haven't touched is still running the very same code it was before. Once all components are exclusively using the v6 APIs, your app no longer needs the compatibility package and is running on v6. The official guide can be found [here][upgrading].
+Instead of upgrading and updating all of your code at once (which is incredibly difficult and prone to bugs), the backwards compatibility package enables you to upgrade one component, one hook, and one route at a time by running both v5 and v6 in parallel. Any code you haven't touched is still running the very same code it was before. Once all components are exclusively using the v6 APIs, your app no longer needs the compatibility package and is running on v6. The official guide can be found [here](https://github.com/remix-run/react-router/discussions/8753).
 
 We recommend using the backwards compatibility package to upgrade apps that have more than a few routes. Otherwise, we hope this guide will help you do the upgrade all at once!
 
@@ -267,7 +267,9 @@ A few important things to notice about v6 in this example:
   automatically detect the best route for the current URL. This prevents bugs
   due to manually putting routes in the wrong order in a `<Switch>`
 
-You may have also noticed that all `<Route children>` from the v5 app changed to `<Route element>` in v6. Assuming you followed the upgrade steps to v5.1, this should be as simple as moving your route element from the child position to a named `element` prop. <!-- (TODO: can we provide a codemod here?) -->
+You may have also noticed that all `<Route children>` from the v5 app changed to `<Route element>` in v6. Assuming you followed the upgrade steps to v5.1, this should be as simple as moving your route element from the child position to a named `element` prop. 
+
+<!-- (TODO: can we provide a codemod here?) -->
 
 ### Advantages of `<Route element>`
 
@@ -885,7 +887,9 @@ This change was made both to follow more closely the convention established by t
   - `useRouteMatch({ sensitive })` is now `useMatch({ caseSensitive })`
 - It returns a match object with a different shape
 
-To see the exact API of the new `useMatch` hook and its type declaration, check out our [API Reference][usematch]. <!-- TODO: Show examples for refactoring useRouteMatch -->
+To see the exact API of the new `useMatch` hook and its type declaration, check out our [API Reference](../hooks/use-match). 
+
+<!-- TODO: Show examples for refactoring useRouteMatch -->
 
 ## `<Prompt>` is not currently supported
 
@@ -896,6 +900,3 @@ To see the exact API of the new `useMatch` hook and its type declaration, check
 Despite our best attempts at being thorough, it's very likely that we missed something. If you follow this upgrade guide and find that to be the case, please let us know. We are happy to help you figure out what to do with your v5 code to be able to upgrade and take advantage of all of the cool stuff in v6.
 
 Good luck 🤘
-
-[upgrading]: https://github.com/remix-run/react-router/discussions/8753
-[usematch]: ../hooks/use-match