Minor improvements to introduction page

docs/src/01.introduction.md

@@ -14,13 +14,17 @@ Firstly, the server will prerender the page and send the prerendered version to
 
 #### Step 2: Render
 
-After the prerendered page is loaded, it will be rendered again. This time, the page will be rendered interactively - meaning that the user will be able to interact with the page after it is rendered. This step happens on the server if you are using the **InteractiveServer** render mode, or on the client (using [webassembly](https://webassembly.org/)) if you are using the **InteractiveWebAssembly** render mode.
+After the prerendered page is loaded, it will be rendered again. This time, the page will be rendered interactively - meaning that the user will be able to interact with the page after it is rendered.
+
+This step happens on the server if you are using the **InteractiveServer** render mode, or on the client (using [webassembly](https://webassembly.org/)) if you are using the **InteractiveWebAssembly** render mode.
 
 #### The problem
 
-The problem with all this is that the state of your components is lost between the prerender and the render steps. This means that if your page contains some **State**, it will be lost when the page is rendered for the second time - which implies initializing the page twice (which may include making WebAPI calls or other expensive operations).
+The problem with all this is that the state of your components is lost between the prerender and the render.
+
+This means that if your page contains some state, it will be lost when the page is rendered for the second time - which implies initializing the page twice (which may include making WebAPI calls or other expensive operations).
 
-The **State** may refer to any kind of data your components posess, such as:
+The **state** may refer to any kind of data your components posess, such as:
 - Data fetched from a WebAPI
 - Data that is expensive to compute
 - etc.