chore: format

Author: remix-run-bot

docs/upgrading/v5.md

@@ -267,7 +267,7 @@ 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. 
+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?) -->
 
@@ -887,7 +887,7 @@ 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](../hooks/use-match). 
+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 -->