ci: apply automated fixes

Author: autofix-ci[bot]

docs/router/framework/react/how-to/use-environment-variables.md

@@ -514,21 +514,22 @@ module.exports = {
 
 **Solutions**:
 
-1. **Add correct prefix**: Use `VITE_` for Vite, `PUBLIC_` for Rspack. 
+1. **Add correct prefix**: Use `VITE_` for Vite, `PUBLIC_` for Rspack.
    Vite's default prefix may be changed in the config:
    ```ts
    // vite.config.ts
    export const config = {
      // ...rest of your config
-     envPrefix: 'MYPREFIX_' // this means `MYPREFIX_MY_VARIABLE` is the new correct way
+     envPrefix: 'MYPREFIX_', // this means `MYPREFIX_MY_VARIABLE` is the new correct way
    }
    ```
-3. **Restart development server** after adding new variables
-4. **Check file location**: `.env` file must be in project root
-5. **Verify bundler configuration**: Ensure variables are properly injected
-6. **Verify variable**:
-  - **In dev**: is in correct `.env` file or environment
-  - **For prod**: is in correct `.env` file or current environment ***at bundle time***. That's right, `VITE_`/`PUBLIC_`-prefixed variables are replaced in a macro-like fashion at bundle time, and will *never* be read at runtime on your server. This is a common mistake, so make sure this is not your case.
+2. **Restart development server** after adding new variables
+3. **Check file location**: `.env` file must be in project root
+4. **Verify bundler configuration**: Ensure variables are properly injected
+5. **Verify variable**:
+
+- **In dev**: is in correct `.env` file or environment
+- **For prod**: is in correct `.env` file or current environment **_at bundle time_**. That's right, `VITE_`/`PUBLIC_`-prefixed variables are replaced in a macro-like fashion at bundle time, and will _never_ be read at runtime on your server. This is a common mistake, so make sure this is not your case.
 
 **Example**:
 
@@ -559,6 +560,7 @@ PUBLIC_API_KEY=abc123 npm run build
 **Solutions**:
 
 Pass variables from the server down to the client:
+
 1. Add your variable to the correct `env.` file
 2. Create an endpoint on your server to read the value from the client
 

docs/start/framework/react/how-to/use-environment-variables.md

@@ -378,15 +378,16 @@ for (const key of requiredClientEnv) {
    // vite.config.ts
    export const config = {
      // ...rest of your config
-     envPrefix: 'MYPREFIX_' // this means `MYPREFIX_MY_VARIABLE` is the new correct way
+     envPrefix: 'MYPREFIX_', // this means `MYPREFIX_MY_VARIABLE` is the new correct way
    }
    ```
 2. **Restart development server** after adding new variables
 3. **Check file location**: `.env` file must be in project root
 4. **Verify bundler configuration**: Ensure variables are properly injected
 5. **Verify variable**:
-  - **In dev**: is in correct `.env` file or environment
-  - **For prod**: is in correct `.env` file or current environment ***at bundle time***. That's right, `VITE_`-prefixed variables are replaced in a macro-like fashion at bundle time, and will *never* be read at runtime on your server. This is a common mistake, so make sure this is not your case.
+
+- **In dev**: is in correct `.env` file or environment
+- **For prod**: is in correct `.env` file or current environment **_at bundle time_**. That's right, `VITE_`-prefixed variables are replaced in a macro-like fashion at bundle time, and will _never_ be read at runtime on your server. This is a common mistake, so make sure this is not your case.
 
 **Example**:
 
@@ -411,6 +412,7 @@ VITE_API_KEY=abc123 npm run build
 **Solutions**:
 
 Pass variables from the server down to the client:
+
 1. Add your variable to the correct `env.` file
 2. Create an endpoint on your server to read the value from the client