Docs/project structure polish

docs/01-app/01-getting-started/02-project-structure.mdx

@@ -52,7 +52,7 @@ Top-level files are used to configure your application, manage dependencies, run
 
 ### Routing Files
 
-Add `page` to expose a route, `layout` for shared UI such as header, nav, or footer, `loading` for skeletons, `error` for error boundaries and `route` for APIs.
+Add `page` to expose a route, `layout` for shared UI such as header, nav, or footer, `loading` for skeletons, `error` for error boundaries, and `route` for APIs.
 
 |                                                                               |                     |                              |
 | ----------------------------------------------------------------------------- | ------------------- | ---------------------------- |
@@ -88,7 +88,7 @@ Parameterize segments with square brackets. Use `[segment]` for a single param,
 | `app/shop/[...slug]/page.tsx`   | `/shop/clothing`, `/shop/clothing/shirts`                            |
 | `app/docs/[[...slug]]/page.tsx` | `/docs`, `/docs/layouts-and-pages`, `/docs/api-reference/use-router` |
 
-### Route Groups and private folders
+### Route groups and private folders
 
 Organize code without changing URLs with route groups [`(group)`](/docs/app/api-reference/file-conventions/route-groups#convention), and colocate non-routable files with private folders [`_folder`](#private-folders).
 
@@ -105,13 +105,13 @@ These features fit specific UI patterns, such as slot-based layouts or modal rou
 
 Use `@slot` for named slots rendered by a parent layout. Use intercept patterns to render another route inside the current layout without changing the URL, for example, to show a details view as a modal over a list.
 
-| Pattern (docs)                                                                              | Meaning              | Typical use case                     |
-| ------------------------------------------------------------------------------------------- | -------------------- | ------------------------------------ |
-| [`@folder`](/docs/app/api-reference/file-conventions/parallel-routes#slots)                 | Named slot           | Sidebar + main content               |
-| [`(.)folder`](/docs/app/api-reference/file-conventions/intercepting-routes#convention)      | Intercept same level | Preview sibling route in a modal     |
-| [`(..)folder`](/docs/app/api-reference/file-conventions/intercepting-routes#convention)     | Intercept parent     | Open parent child as overlay         |
-| [`(..)(..)folder`](/docs/app/api-reference/file-conventions/intercepting-routes#convention) | Intercept two levels | Deeply nested overlay                |
-| [`(...)folder`](/docs/app/api-reference/file-conventions/intercepting-routes#convention)    | Intercept from root  | Show arbitrary route in current view |
+| Pattern (docs)                                                                              | Meaning              | Typical use case                         |
+| ------------------------------------------------------------------------------------------- | -------------------- | ---------------------------------------- |
+| [`@folder`](/docs/app/api-reference/file-conventions/parallel-routes#slots)                 | Named slot           | Sidebar + main content                   |
+| [`(.)folder`](/docs/app/api-reference/file-conventions/intercepting-routes#convention)      | Intercept same level | Preview sibling route in a modal         |
+| [`(..)folder`](/docs/app/api-reference/file-conventions/intercepting-routes#convention)     | Intercept parent     | Open a child of the parent as an overlay |
+| [`(..)(..)folder`](/docs/app/api-reference/file-conventions/intercepting-routes#convention) | Intercept two levels | Deeply nested overlay                    |
+| [`(...)folder`](/docs/app/api-reference/file-conventions/intercepting-routes#convention)    | Intercept from root  | Show arbitrary route in current view     |
 
 ### Metadata file conventions
 
@@ -147,7 +147,7 @@ Use `@slot` for named slots rendered by a parent layout. Use intercept patterns
 
 <PagesOnly>
 
-### Files conventions
+### File conventions
 
 |                                                                                                             |                     |                   |
 | ----------------------------------------------------------------------------------------------------------- | ------------------- | ----------------- |
@@ -197,7 +197,7 @@ The components defined in special files are rendered in a specific hierarchy:
 - `template.js`
 - `error.js` (React error boundary)
 - `loading.js` (React suspense boundary)
-- `not-found.js` (React error boundary)
+- `not-found.js` (React error boundary for "not found" UI)
 - `page.js` or nested `layout.js`
 
 <Image