fix(doc): fix markdown bug in compatibility.mdx (#7138)

Author: vegerot

packages/document/main-doc/docs/en/guides/advanced-features/compatibility.mdx

@@ -26,7 +26,7 @@ Please refer to [Rsbuild - Browserslist](https://rsbuild.dev/guide/advanced/brow
 
 ### Polyfill At Compile
 
-Modern.js defaults to importing corresponding polyfill code from [core-js] (https://github.com/zloirock/core-js) during compilation.
+Modern.js defaults to importing corresponding polyfill code from [core-js](https://github.com/zloirock/core-js) during compilation.
 
 By default, the required Polyfill code will be introduced according to the settings of the Browserslist, so there is no need to worry about the Polyfill problem of the project source code and third-party dependencies, but because it contains some Polyfill code that is not used, the final bundle size may be increased.
 

packages/document/main-doc/docs/en/guides/basic-features/data/data-fetch.mdx

@@ -149,9 +149,10 @@ Having the `loader` function run only on the server in SSR applications brings s
 - **Simplifies usage**: Guarantees consistent data-fetching methods in SSR applications, so developers don't have to distinguish between client and server code.
 - **Reduces client bundle size**: Moves logic code and dependencies from the client to the server.
 - **Improves maintainability**: Less direct influence of data logic on front-end UI and avoids issues of accidentally including server dependencies in the client bundle or vice versa.
+
 :::
 
-We recommend using the `fetch` API in `loader` functions to make requests. Modern.js provides a default polyfill for the `fetch` API, allowing it to be used on the server. This means you can fetch data in a consistent manner whether in CSR or SSR:
+We recommend using the `fetch` API in `loader` functions to make requests. Since `fetch` works similarly on the client and server, you can fetch data in a consistent manner whether in CSR or SSR:
 
 ```tsx
 export async function loader() {

packages/document/main-doc/docs/en/guides/basic-features/render/ssr.mdx

@@ -1,6 +1,6 @@
 # Server-Side Rendering
 
-Server-Side Rendering (SSR) involves rendering the HTML content of a webpage-side and then sending the fully-rendered page to the browser. The browser only needs to display the page without additional rendering.
+Server-Side Rendering (SSR) involves rendering the HTML content of a webpage server-side and then sending the fully-rendered page to the browser. The browser only needs to display the page without additional rendering.
 
 The main advantages are:
 
@@ -320,4 +320,4 @@ In this case, the `epicMiddleware` instance is created outside the component, an
 
 This code does not cause issues on the client-side. However, in SSR, the Middleware instance remains non-disposable. Each time the component renders, calling `epicMiddleware.run(rootEpic)` adds new event bindings internally, causing the entire object to grow continuously, ultimately affecting application performance.
 
-Such issues are not easily noticed in CSR. When transitioning from CSR to SSR, if you're unsure whether your application has such hidden pitfalls, consider stress testing the application.
+Such issues are not easily noticed in CSR. When transitioning from CSR to SSR, if you're unsure whether your application has such hidden pitfalls, consider stress testing the application.

packages/document/main-doc/docs/en/guides/concept/entries.mdx

@@ -76,7 +76,7 @@ By default, Modern.js scans the files under `src/` before starting the project,
 
 :::tip
 
-- You can custom the recognition directory for page entries by using [source.entriesDir](/configure/app/source/entries-dir).
+- You can customize the recognition directory for page entries by using [source.entriesDir](/configure/app/source/entries-dir).
 - If you need to customize the entry points, please refer to [Custom Entries](#custom-entries).
 
 :::

packages/document/main-doc/docs/en/tutorials/first-app/c05-loader.mdx

@@ -7,7 +7,7 @@ In the previous chapter, we learned how to add client route.
 
 In this chapter, we will learn how to add **Loader** to the routing component.
 
-By far, we have provided data to components through hardcoding. If you want to get data from the remote, you usually use `useEffect` to do it. But when SSR is enabled, `useEffect` will not be executed at the server level, so this SSR can only render a very limited UI.
+So far, we have provided data to components through hardcoding. If you want to get data from the remote, you usually use `useEffect` to do it. But when SSR is enabled, `useEffect` will not be executed at the server level, so this SSR can only render a very limited UI.
 
 Modern.js provides the ability of Data Loader to support homogeneous data acquisition in components to maximize the value of SSR.
 

packages/generator/generators/entry-generator/templates/routes/page.handlebars

@@ -79,14 +79,14 @@ const Index = () => (
           className="card"
         >
           <h2>
-            Github
+            GitHub
             <img
               className="arrow-right"
               src="https://lf3-static.bytednsdoc.com/obj/eden-cn/zq-uylkvT/ljhwZthlaukjlkulzlp/arrow-right.svg"
               alt="Github"
             />
           </h2>
-          <p>View the source code of Github, feel free to contribute.</p>
+          <p>View the source code on GitHub; feel free to contribute.</p>
         </a>
       </div>
     </main>

packages/runtime/plugin-runtime/src/router/runtime/plugin.node.tsx

@@ -110,7 +110,7 @@ export const routerPlugin = (
           basename: _basename,
         });
 
-        // We can't pass post request to query,due to post request would triger react-router submit action.
+        // We can't pass post request to query,due to post request would trigger react-router submit action.
         // But user maybe do not define action for page.
         const remixRequest = createRemixReuqest(
           context.ssrContext!.request.raw,
@@ -145,13 +145,13 @@ export const routerPlugin = (
         }
 
         const router = createStaticRouter(routes, routerContext);
-        // routerContext is used in in css colletor、handle status code、inject loader data in html
+        // routerContext is used in in css collector、handle status code、inject loader data in html
         context.routerContext = routerContext;
 
         // private api, pass to React Component in `wrapRoot`
         // in the browser, we not need to pass router, cause we create Router in `wrapRoot`
         // but in node, we need to pass router, cause we need run async function, it can only run in `beforeRender`
-        // when we deprected React 17, we can use Suspense to handle this async function
+        // when we deprecated React 17, we can use Suspense to handle this async function
         // so the `remixRouter` has no type declare in RuntimeContext
         context.remixRouter = router;