revert changes from weird git issue

docs/framework/react/decisions-on-dx.md

@@ -205,7 +205,7 @@ export const postsIndexRoute = createRoute({
 
 All of this boilerplate, no matter how essential for providing a best-in-class type-inference experience, can be a bit overwhelming and can lead to inconsistencies and errors in the route configuration.
 
-... and this example configuration is just for rendering a single code-split route. Imagine having to do this for 40-50 routes. Now remember that you still haven't touched the `context`, `loaders`, `search param validation`, and other features of the router 🤕.
+... and this example configuration is just for rendering a single codes-split route. Imagine having to do this for 40-50 routes. Now remember that you still haven't touched the `context`, `loaders`, `search param validation`, and other features of the router 🤕.
 
 > So, why's file-based routing the preferred way?
 

docs/framework/react/guide/code-splitting.md

@@ -115,7 +115,7 @@ Since TanStack Router's file-based routing system is designed to support both fl
 
 To encapsulate a route's files into a directory, move the route file itself into a `.route` file within a directory with the same name as the route file.
 
-For example, if you have a route file named `posts.tsx`, you would create a new directory named `posts` and move the `posts.tsx` file into that directory, renaming it to `route.tsx`.
+For example, if you have a route file named `posts.tsx`, you would create a new directory named `posts` and move the `posts.tsx` file into that directory, renaming it to `index.route.tsx`.
 
 #### Before
 
@@ -125,8 +125,8 @@ For example, if you have a route file named `posts.tsx`, you would create a new
 #### After
 
 - `posts`
-  - `index.route.tsx`
-  - `index.route.lazy.tsx`
+  - `route.tsx`
+  - `route.lazy.tsx`
 
 ### Virtual Routes
 

docs/framework/react/guide/route-trees.md

@@ -9,7 +9,7 @@ To build a route tree, TanStack Router supports both:
 - File-Based Routing
 - Code-Based Routing
 
-Both methods support the exact same core features and functionality, but **file-based routing requires less code for the same or better results**. For this reason, **file-based routing is the preferred and recommended way to configure TanStack Router and most of the documentation is written from the perspective of file-based routing**
+Both methods support the exact same core features and functionality, but **file-based routing requires less code for the same or better results**. For this reasons, **file-based routing is the preferred and recommended way to configure TanStack Router and most of the documentation is written from the perspective of file-based routing**
 
 For code-based routing documentation, please see
 the [Code-Based Routing](../code-based-routing) guide.