chore: format

docs/guides/routing.md

@@ -74,7 +74,6 @@ app
     └── sales.tsx
 ```
 
-
 - `root.tsx` is the "root route" that serves as the layout for the entire application. Every route will render inside its `<Outlet/>`.
 - Note that there are files with `.` delimiters. The `.` creates a `/` in the URL for that route, as well as layout nesting with another route that matches the segments before the `.`. For example, `sales.tsx` is the **parent route** for all the **child routes** that look like `sales.[the nested path].tsx`. The `<Outlet />` in `sales.tsx` will render the matching child route.
 - The `_index.tsx` routes will render inside the parent `<Outlet>` when the url is only as deep as the parent's path (like `example.com/sales` instead of `example.com/sales/customers`)

docs/pages/api-development-strategy.md

@@ -50,11 +50,11 @@ The lifecycle is thus either:
 
 ## Current Future Flags
 
-| Flag                 | Description                                                     |
-| -------------------- | --------------------------------------------------------------- |
-| `v2_dev`             | Enable the new development server (including HMR/HDR support)   |
-| `v2_headers`         | Leverage ancestor `headers` if children do not export `headers` |
-| `v2_meta`            | Enable the new API for your `meta` functions                    |
+| Flag         | Description                                                     |
+| ------------ | --------------------------------------------------------------- |
+| `v2_dev`     | Enable the new development server (including HMR/HDR support)   |
+| `v2_headers` | Leverage ancestor `headers` if children do not export `headers` |
+| `v2_meta`    | Enable the new API for your `meta` functions                    |
 
 [future-flags-blog-post]: https://remix.run/blog/future-flags
 [feature-flowchart]: /docs-images/feature-flowchart.png