Fix some grammar and typo issues (#941)

Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
Co-authored-by: Sarah <gerrardsarah@gmail.com>

Author: 3 people

src/routes/configuration/environment-variables.mdx

@@ -59,7 +59,7 @@ function MyComponent() {
 
 ## Private Environment Variables
 
-These variables should only be accessed in your backend code, and so it's best to not use `VITE_` prefix for them. Instead, use `process.env` to access them. Depending on the [Nitro preset](https://nitro.unjs.io/deploy) chosen, they'll be made available automatically or they will require an external dependency such as [dotenv](https://www.npmjs.com/package/dotenv).
+These variables should only be accessed in your backend code, so it's best not to use the `VITE_` prefix for them. Instead, use `process.env` to access them. Depending on the [Nitro preset](https://nitro.unjs.io/deploy) chosen, they'll be made available automatically or they will require an external dependency such as [dotenv](https://www.npmjs.com/package/dotenv).
 
 ```jsx
 DB_HOST="somedb://192.110.0"

src/routes/configuration/typescript.mdx

@@ -589,7 +589,7 @@ return (
 );
 ```
 
-This approach is similar using the keyed option, but offers an accessor to prevent the recreation of children each time the `when` value changes.
+This approach is similar to using the keyed option, but offers an accessor to prevent the recreation of children each time the `when` value changes.
 
 ```tsx
 return (

src/routes/guides/routing-and-navigation.mdx

@@ -362,7 +362,7 @@ Wildcard tokens **must** be the last part of the path; `foo/*any/bar` will not c
 ### Multiple paths
 
 The `Routes` component also supports defining multiple paths using an array.
-This allows avoids a route rerendering when switching between two or more locations that it matches:
+This avoids a route rerendering when switching between two or more locations that it matches:
 
 ```jsx
 // Navigating from "/login" to "/register" will not cause the component to re-render

src/routes/guides/state-management.mdx

@@ -3,7 +3,7 @@ title: State management
 order: 2
 ---
 
-State management is process of handling and manipulating data that affects the behavior and presentation of a web application.
+State management is the process of handling and manipulating data that affects the behavior and presentation of a web application.
 To build interactive and dynamic web applications, state management is a critical aspect of development.
 Within Solid, state management is facilitated through the use of reactive primitives.
 

src/routes/guides/styling-components/css-modules.mdx

@@ -11,7 +11,7 @@ These provide a way to encapsulate styles within components, preventing global c
 
 Begin by creating a CSS module file.
 Conventionally, these files have a `.module.css` extension, like `style.module.css`.
-However, you can also use other other extensions, such as `.scss` and `.sass`.
+However, you can also use other extensions, such as `.scss` and `.sass`.
 
 ```css
 /* styles.module.css */

src/routes/reference/basic-reactivity/create-effect.mdx

@@ -73,7 +73,7 @@ queueMicrotask(() => {
 // goodbye
 ```
 
-This delay in first execution is useful because it means an effect defined in a component scope runs after the JSX returned by the component gets added the DOM.
+This delay in first execution is useful because it means an effect defined in a component scope runs after the JSX returned by the component gets added to the DOM.
 In particular, [refs](/reference/jsx-attributes/ref) will already be set.
 Thus you can use an effect to manipulate the DOM manually, call vanilla JS libraries, or other side effects.