some quick corrections

Author: michaelessiet

content/references/concepts/ssr/ssg.mdx

@@ -1,6 +1,6 @@
 import {Aside} from '~/components/configurable/Aside'
 
-<Title>Server-Side Generation (SSG)</Title>
+<Title>Static Site Generation (SSG)</Title>
 
 <Aside type="advanced">
   This is a low level API intended for use by library authors. If you would like to use static site generation in your application we suggest making use of [Solid Start](https://start.solidjs.com/getting-started/what-is-solidstart) our meta-framework that makes adding server side rendering to your appkication extremely easy.
@@ -10,23 +10,23 @@ In this section we will be talking about static site generation and how you can
 
 ## What is Static Site Generation?
 
-Static site generation is the process of generating a static (never changing) HTML website based on raw data and templates developed using web development frameworks like Solid.js.
+Static site generation is the process of generating a static (never changing) HTML website based on raw data through the use of web development frameworks like Solid.js.
 
 Static sites are made up of HTML that loads up the same way every time, in opposition to dynamic website where data on the site can change based on the user input or changes in fetched data.
 
 ## How does Solid.js implement SSG?
 
-Solid.js makes use of the [renderToStringAsync](/references/concepts/ssr/async-ssr) function in order to load all the asynchronous data and generate the HTML required.
+Solid.js makes use of the [`renderToStringAsync`](/references/concepts/ssr/async-ssr) function in order to load all the asynchronous data and generate the HTML required.
 
-You might be wondering what makes this any different from Async SSR then? Well the key difference between this and Async SSR is that in Async SSR the server runs the Solid.js app while in SSG the output is stored ahead of time and the Solid.js code isn't touched again aside from in build time during updates.
+You might be wondering what makes this any different from Async SSR then? Well the key difference between this and Async SSR is that in Async SSR the server runs the Solid.js app while in SSG the Solid.js app is compiled and has it's ouput stored ahead of time. Meaning the Solid.js code isn't touched again aside from in build time during updates.
 
 This might sound a little vague and hard to understand so here's an example of how it looks in action.
 
 ## How to use SSG in Solid.js?
 
-<Aside type="general"> This process of implementing SSG in Solid.js is more complicated that implementing any other form of SSR, so please follow along carefully </Aside>
+<Aside type="general"> This process of implementing SSG in Solid.js is more complicated when compared to implementing other forms of SSR in Solid.js, so please follow along carefully </Aside>
 
-In order to make use of SSG in Solid.js you'll need to have a bundler that helps in bundling JS code. In this example we will be making use of Rollup.
+In order to make use of SSG in Solid.js you'll need to have a compiler that helps in compiling JS code. In this example we will be making use of Rollup.
 
 ```js
 // rollup.config.js
@@ -83,7 +83,7 @@ export default [
 ];
 ```
 
-In the code above we're setting up rollup to help us bundle our code by turning all the jsx we have into compiled javascript that we'll be able to later run using `node`
+In the code above we're setting up rollup to help us compile our code by turning all the jsx we have into compiled javascript that we'll be able to later run using `node`
 
 Next let's create our `App.jsx`
 
@@ -99,7 +99,7 @@ export default function App() {
 }
 ```
 
-Above is a simple component. You can make use of asynchronous data if you would like to since we'll be making use of the `renderToStringAsync` function.
+Above is a simple component. You can make use of asynchronous data if you would like to since we'll be making use of the `renderToStringAsync` function all asynchronous data will be fetched and put in place before building the site.
 
 Now we'll be creating an index.js file which rollup will be compiling and turning into a CommonJS file with all the jsx and tsx code transformed, compiled and ready to run.
 
@@ -141,7 +141,7 @@ renderStatic(
 
 This will help us generate our static files using the `renderStatic` function provided by the `solid-ssr` package.
 
-Now all that's left is to build, run our script and serve our static site.
+Now all that's left is to compile our code, run our script and serve our static site.
 
 ```bash
 npx rollup -c rollup.config.js && node generate.js #compile and generate the site

src/NAV_SECTIONS.ts

@@ -72,7 +72,7 @@ export const REFERENCE_SECTIONS: SECTIONS = {
             link: "/references/concepts/ssr/streaming",
           },
           {
-            name: "Server-Side Generation (SSG)",
+            name: "Static Site Generation (SSG)",
             link: "/references/concepts/ssr/ssg",
           },
           {