docs: minor docs improvements

docs/router/guide/code-splitting.md

@@ -115,7 +115,7 @@ These are the only options that `createLazyFileRoute` supports:
 
 ### Example code splitting with `.lazy.tsx`
 
-When you are using `.lazy.tsx` you can split your route into two files to enable code splitting:
+When you are using `.lazy.tsx`, you can split your route into two files to enable code splitting:
 
 **Before (Single File)**
 

docs/router/routing/code-based-routing.md

@@ -14,7 +14,7 @@ title: Code-Based Routing
 
 Code-based routing is no different from file-based routing in that it uses the same route tree concept to organize, match and compose matching routes into a component tree. The only difference is that instead of using the filesystem to organize your routes, you use code.
 
-Let's consider the same route tree from the [Route Trees & Nesting](./route-trees.md#route-trees) guide, and convert it to code-based routing:
+Let's consider the same route tree from the [Route Trees](./route-trees.md#route-trees) guide, and convert it to code-based routing:
 
 Here is the file-based version:
 

docs/router/routing/file-based-routing.md

@@ -12,7 +12,7 @@ File-based routing is a way to configure your routes using the filesystem. Inste
 - **Organization**: Routes are organized in a way that mirrors the URL structure of your application.
 - **Scalability**: As your application grows, file-based routing makes it easy to add new routes and maintain existing ones.
 - **Code-Splitting**: File-based routing allows TanStack Router to automatically code-split your routes for better performance.
-- **Type-Safety**: File-based routing raises the ceiling on type-safety by generating managing type linkages for your routes, which can otherwise be a tedious process via code-based routing.
+- **Type-Safety**: File-based routing raises the ceiling on type-safety by generating and managing type linkages for your routes, which can otherwise be a tedious process via code-based routing.
 - **Consistency**: File-based routing enforces a consistent structure for your routes, making it easier to maintain and update your application and move from one project to another.
 
 ## `/`s or `.`s?
@@ -80,7 +80,7 @@ See the example below:
 
 ## Mixed Flat and Directory Routes
 
-It's extremely likely that a 100% directory or flat route structure won't be the best fit for your project, which is why TanStack Router allows you to mix both flat and directory routes together to create a route tree that uses the best of both worlds where it makes sense:
+It's extremely likely that a 100% directory or flat route structure won't be the best fit for your project, which is why TanStack Router allows you to mix both flat and directory routes together to create a route tree that uses the best of both worlds where it makes sense.
 
 See the example below:
 

docs/router/routing/file-naming-conventions.md

@@ -2,7 +2,7 @@
 title: File Naming Conventions
 ---
 
-File-based routing requires that you follow a few simple file naming conventions to ensure that your routes are generated correctly. The concepts these conventions enable are covered in detail in the [Route Trees & Nesting](./route-trees.md) guide.
+File-based routing requires that you follow a few simple file naming conventions to ensure that your routes are generated correctly. The concepts these conventions enable are covered in detail in the [Route Trees](./route-trees.md) guide.
 
 | Feature                            | Description                                                                                                                                                                                                                                                                                                                                                                                                          |
 | ---------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -40,4 +40,4 @@ Pathless routes wrap child routes with either logic or a component without requi
 | ʦ `_app.a.tsx` | /a         | `<Root><App><A>` |
 | ʦ `_app.b.tsx` | /b         | `<Root><App><B>` |
 
-To learn more about pathless routes, see the [Routing Concepts - Pathless Routes](./routing-concepts.md#pathless-layout-routes) guide.
+To learn more about pathless routes, see the [Routing Concepts - Pathless Layout Routes](./routing-concepts.md#pathless-layout-routes) guide.

docs/router/routing/routing-concepts.md

@@ -564,7 +564,7 @@ routes/
 │   ├── ...
 ```
 
-We can import from the excluded files into our posts route
+We can import from the excluded files into our posts route:
 
 <!-- ::start:framework -->