Fix typo

Author: amirhhashemi

src/routes/solid-start/building-your-application/api-routes.mdx

@@ -6,7 +6,7 @@ While Server Functions can be a good way to write server-side code for data need
 Some reasons for wanting API Routes include:
 - There are additional clients that want to share this logic.
 - Exposing a GraphQL or tRPC endpoint.
-- Exposing a public facing REST API.
+- Exposing a public-facing REST API.
 - Writing webhooks or auth callback handlers for OAuth.
 - Having URLs not serving HTML, but other kinds of documents like PDFs or images.
 

src/routes/solid-start/building-your-application/css-and-styling.mdx

@@ -78,7 +78,7 @@ This is because, behind the scenes, classes defined in CSS modules are renamed t
 When classes are hard coded using the class attribute (`class="card"`), Solid is not aware that it should rename `card` to something different.
 
 To fix this, you can import classes used in your CSS module.
-The import object can be thought of as `humanClass: generatedClass` and within the component, they key (ie. the class on the element) is used to get the unique, generated class name.
+The import object can be thought of as `humanClass: generatedClass` and within the component, the key (ie. the class on the element) is used to get the unique, generated class name.
 
 ```jsx
 import styles from "./Card.module.css";

src/routes/solid-start/building-your-application/head-and-metadata.mdx

@@ -38,7 +38,7 @@ export default function About() {
 These tags will be applied for that specific route only and will be removed from `document.head` once a user navigates away from the page. 
 `routeData` can also be used here to create titles and SEO metadata that is specific to the dynamic parts of the route.
 
-## Adding a site-suffix in Title
+## Adding a site suffix in Title
 
 Custom components can be created to wrap the `Title` component to add a site-specific prefix to all the titles:
 
@@ -112,7 +112,7 @@ export default function Root() {
 }
 ```
 
-If you need to add route specific information inside your route, much like the `Title` component, you can use the `Meta` component within the desired route.
+If you need to add route-specific information inside your route, much like the `Title` component, you can use the `Meta` component within the desired route.
 This overrides the `Meta` tags used within the `Head` component.
 
 ```tsx

src/routes/solid-start/building-your-application/route-prerendering.mdx

@@ -3,7 +3,7 @@ title: "Route pre-rendering"
 ---
 
 SolidStart offers a way to pre-render pages at build time.
-The easiest way to accomplish this, is by passing a list of routes to be pre-rendered to the `routes` option.
+The easiest way to accomplish this is by passing a list of routes to be pre-rendered to the `routes` option.
 
 ```js { 6 }
 import { defineConfig } from "@solidjs/start/config";
@@ -31,4 +31,4 @@ export default defineConfig({
 });
 ```
 
-For more information on prerender options, check out [Nitro's documentation](https://nitro.unjs.io/config#prerender)
+For more information on prerender options, check out [Nitro's documentation](https://nitro.unjs.io/config#prerender)

src/routes/solid-start/building-your-application/routing.mdx

@@ -2,7 +2,7 @@
 title: "Routing"
 ---
 
-Routing serves as a key component to web applications.
+Routing serves as a key component of web applications.
 Within SolidStart, there are two types:
 
 - **UI routes** — define the user interface in your app
@@ -16,11 +16,11 @@ SolidStart uses file based routing which is a way of defining your routes by cre
 This includes your pages and API routes.
 
 SolidStart traverses your `routes` directory, collects all of the routes, and then makes them accessible using the [`<FileRoutes />`](/solid-start/reference/routing/file-routes).
-This component will only include your UI routes, and not your API routes.
+This component will only include your UI routes and not your API routes.
 Rather than manually defining each `Route` inside a `Router` component, `<FileRoutes />` will generate the routes for you based on the file system.
 
 Because `<FileRoutes />` returns a routing config object, you can use it with the router of your choice.
-In this example we use [`solid-router`](/solid-router):
+In this example, we use [`solid-router`](/solid-router):
 
 ```tsx {7-9} title="app.tsx"
 import { Suspense } from "solid-js";
@@ -37,7 +37,7 @@ export default function App() {
 ```
 
 The `<Router />` component expects a `root` prop which functions as the root layout of your entire app.
-You will want to make sure `props.children` is wrapped in `<Suspense />` because each component will be lazy loaded automatically for you. Without this you may see some unexpected hydration errors.
+You will want to make sure `props.children` is wrapped in `<Suspense />` because each component will be lazy-loaded automatically for you. Without this you may see some unexpected hydration errors.
 
 `<FileRoutes />` will generate a route for each file in the `routes` directory and its subdirectories. For a route to be rendered as a page, it must default export a component.
 This component represents the content that will be rendered when users visit the page:
@@ -84,7 +84,7 @@ If you want to create nested layouts you can create a file with the same name as
         |-- article-2.tsx        // example.com/blog/article-2
 ```
 
-In this case the `blog.tsx` file will act as a layout for the articles in the `blog` folder. You can reference the child content
+In this case, the `blog.tsx` file will act as a layout for the articles in the `blog` folder. You can reference the child's content
 by using `props.children` in the layout.
 
 <TabsCodeBlocks>
@@ -113,7 +113,7 @@ export default function BlogLayout(props) {
 By default, the component that is rendered for a route comes from the default export of the `index.tsx` file in each folder.
 However, this can make it difficult to find the correct `index.tsx` file when searching, since there will be multiple files with that name.
 
-To avoid this, you can rename the `index.tsx` file to the name of the folder it is in, enclosed in parenthesis.
+To avoid this, you can rename the `index.tsx` file to the name of the folder it is in, enclosed in parentheses.
 
 This way, it will be treated as the default export for that route:
 

src/routes/solid-start/building-your-application/static-assets.mdx

@@ -69,10 +69,10 @@ For example, `solid.png` will become `solid.2d8efhg.png`.
 ## Public directory versus imports
 
 The public directory and imports are both valid ways to include static assets in your project.
-The driver to using one over the other is based on your use case.
+The driver to use one over the other is based on your use case.
 
 For dynamic updates to your assets, using the public directory is the best choice. 
 It allows you to maintain full control over the asset URL paths, ensuring that the links remain consistent even when the assets are updated.
 
 When using imports, the filename is hashed and therefore will not be predictable over time. 
-This can be beneficial for cache busting but detrimental if you want to send someone a link to the asset.
+This can be beneficial for cache busting but detrimental if you want to send someone a link to the asset.