Docs: improve writings on docs/getting_started (#24014)

- Change "Windows 8" to just "Windows"
- Change "start screen" to "start menu" (as it's more common in many versions of Windows)
- Improve grammar
- Fix typo

Author: damzaky

site/source/docs/getting_started/FAQ.rst

@@ -18,7 +18,7 @@ Why do I get errors building basic code and the tests?
 
 All the tests in the :ref:`Emscripten test suite <emscripten-test-suite>` are
 known to build and pass on our test infrastructure, so if you see failures
-locally it is likely that there is some problem with your environment. (Rarely,
+locally, it is likely that there is some problem with your environment. (Rarely,
 there may be temporary breakage, but never on a tagged release version.)
 
 First call ``emcc --check``, which runs basic sanity checks and prints out
@@ -105,13 +105,13 @@ compilation time).
 Why is my compiled code big?
 ============================
 
-Make sure you build with ``-O3`` or ``-Os`` so code is fully optimized and
+Make sure you build with ``-O3`` or ``-Os``, so the code is fully optimized and
 minified. You should use the closure compiler, gzip compression on your
 webserver, etc., see the :ref:`section on code size in Optimizing code
 <optimizing-code-size>`.
 
 
-Why does compiling code that works on another machine gives me errors?
+Why does compiling code that works on another machine give me errors?
 ======================================================================
 
 Make sure you are using the Emscripten bundled system headers. Using :ref:`emcc
@@ -207,11 +207,11 @@ JavaScript that does not complete and return control to the browser.
 Graphical C++ apps typically have an infinite main loop in which event handling,
 processing and rendering is done, followed by a delay to keep the frame-rate
 right (``SDL_DELAY`` in :term:`SDL` apps). As the main loop does not complete
-(is infinite) it cannot return control to the browser, and the app will hang.
+(is infinite), it cannot return control to the browser, and the app will hang.
 
 Apps that use an infinite main loop should be re-coded to put the actions for a
 single iteration of the loop into a single "finite" function. In the native
-build this function can be run in an infinite loop as before. In the Emscripten
+build, this function can be run in an infinite loop as before. In the Emscripten
 build it is set as the :ref:`main loop function <faq-how-run-event-loop>` and
 will be called by the browser at a specified frequency.
 

site/source/docs/getting_started/Tutorial.rst

@@ -28,18 +28,18 @@ using ``./emcc`` or ``./em++``.
 For the next section you will need to open a command prompt:
 
 - On Linux or macOS, open a *Terminal*.
-- On Windows open the :ref:`Emscripten Command Prompt <emcmdprompt>`, a command
+- On Windows, open the :ref:`Emscripten Command Prompt <emcmdprompt>`, a command
   prompt that has been pre-configured with the correct system paths and settings
   to point to the :term:`active <Active Tool/SDK>` Emscripten tools. To access
-  this prompt, type **Emscripten** in the Windows 8 start screen, and then
+  this prompt, type **Emscripten** in the Windows start menu, and then
   select the **Emscripten Command Prompt** option.
 
 Navigate with the command prompt to the emscripten directory under the SDK. This
 is a folder below the :term:`emsdk root directory`, typically
 **<emsdk root directory>/upstream/emscripten/**.
 The examples below will depend on finding files relative to that location.
 
-.. note:: In older emscripten versions the directory structure was different:
+.. note:: In older emscripten versions, the directory structure was different:
    the version number appeared, and the backend (fastcomp/upstream) did not, so
    you would use something like **<emsdk root directory>/emscripten/1.20.0/**.
 
@@ -52,7 +52,7 @@ If you haven't run Emscripten before, run it now with: ::
     ./emcc -v
 
 If the output contains warnings about missing tools, see
-:ref:`verifying-the-emscripten-environment` for debugging help. Otherwise
+:ref:`verifying-the-emscripten-environment` for debugging help. Otherwise,
 continue to the next sections where we'll build some code.
 
 
@@ -61,7 +61,7 @@ Running Emscripten
 
 You can now compile your first C/C++ file to JavaScript.
 
-First, lets have a look at the file to be compiled: **hello_world.c**. This is
+First, let's have a look at the file to be compiled: **hello_world.c**. This is
 the simplest test code in the SDK, and as you can see, all it does is print
 "hello, world!" to the console and then exit.
 
@@ -86,15 +86,6 @@ execute it. You can run them using :term:`node.js`:
 
 This prints "hello, world!" to the console, as expected.
 
-.. note:: Older node.js versions do not have WebAssembly support yet. In that
-   case you will see an error message suggesting that you build with
-   ``-sWASM=0`` to disable WebAssembly, and then emscripten will emit the compiled
-   code as JavaScript. In general, WebAssembly is recommended as it has
-   widespread browser support and is more efficient both to execute and to
-   download (and therefore emscripten emits it by default), but sometimes you
-   may need your code to run in an environment where it is not yet present and
-   so should disable it.
-
 .. tip:: If an error occurs when calling *emcc*, run it with the ``-v`` option
    to print out a lot of useful debug information.
 
@@ -116,11 +107,11 @@ file as the target file: ::
 
 You can now open ``hello.html`` in a web browser.
 
-.. note:: Unfortunately several browsers (including *Chrome*, *Safari*, and
-   *Internet Explorer*) do not support ``file://`` :term:`XHR` requests, and
-   can't load extra files needed by the HTML (like a ``.wasm`` file, or packaged
-   file data as mentioned lower down). For these browsers you'll need to serve
-   the files using a :ref:`local webserver <faq-local-webserver>` and then open
+.. note:: Unfortunately, several browsers (including *Chrome* and *Safari*) do
+   not support ``file://`` :term:`XHR` requests, and can't load extra files
+   needed by the HTML (like a ``.wasm`` file, or packaged file data as mentioned
+   lower down). For these browsers, you'll need to serve the files using a
+   :ref:`local webserver <faq-local-webserver>` and then open
    ``http://localhost:8000/hello.html``).
 
 Once you have the HTML loaded in your browser, you'll see a text area for

site/source/docs/getting_started/downloads.rst

@@ -8,20 +8,20 @@ Download and install
    <installing-from-source>` if you prefer that to downloading binaries using
    the emsdk.
 
-.. tip:: if you'd like to install emscripten using the **unofficial** packages
+.. tip:: If you'd like to install emscripten using the **unofficial** packages
    instead of the **officially supported** emsdk, see the bottom of the page.
 
 .. _sdk-installation-instructions:
 
 Installation instructions using the emsdk (recommended)
 =======================================================
 
-First check the :ref:`Platform-specific notes
+First, check the :ref:`Platform-specific notes
 <platform-notes-installation_instructions-SDK>` below and install any
 prerequisites.
 
 The core Emscripten SDK (emsdk) driver is a Python script. You can get it for
-the first time with
+the first time with:
 
   ::
 
@@ -52,7 +52,7 @@ GitHub and set them as :term:`active <Active Tool/SDK>`:
     # Activate PATH and other environment variables in the current terminal
     source ./emsdk_env.sh
 
-  .. tip:: If you want to avoid executing `source ./emsdk_env.sh` every time you open a new terminal you can follow the instructions given by the `emsdk activate` command above to add this command to your startup scripts.
+  .. tip:: If you want to avoid executing `source ./emsdk_env.sh` every time you open a new terminal, you can follow the instructions given by the `emsdk activate` command above to add this command to your startup scripts.
 
   .. note:: On Windows, run ``emsdk.bat`` instead of ``./emsdk``, and ``emsdk_env.bat`` instead of ``source ./emsdk_env.sh``.
 
@@ -67,7 +67,7 @@ commands.
 Emsdk install targets
 ---------------------
 
-In the description above we asked the emsdk to install and activate ``latest``,
+In the description above, we asked the emsdk to install and activate ``latest``,
 which is the latest tagged release. That is often what you want.
 
 You can also install a specific version by specifying it, for example,
@@ -101,7 +101,7 @@ target, and note that you must specify the backend explicitly,
     # Get a tip-of-tree 
     ./emsdk install tot
 
-(In the above examples we installed the various targets; remember to also
+(In the above examples, we installed the various targets; remember to also
 ``activate`` them as in the full example from earlier.)
 
 .. _platform-notes-installation_instructions-SDK:
@@ -122,8 +122,8 @@ macOS
 
 .. note:: Emscripten requires macOS 10.14 Mojave or above.
 
-If you use the Emscripten SDK it includes a bundled version of Python 3.
-Otherwise you will need to manually install and use Python 3.6 or newer.
+If you use the Emscripten SDK, it includes a bundled version of Python 3.
+Otherwise, you will need to manually install and use Python 3.6 or newer.
 
 These instructions explain how to install **all** the :ref:`required tools
 <toolchain-what-you-need>`. You can :ref:`test whether some of these are already

site/source/docs/getting_started/test-suite.rst

@@ -99,7 +99,7 @@ the first failure.
    that are normally run in parallel you can force them to run serially using
    ``-j1``.
 
-One a test is fixed you continue where you left off using ``--start-at`` option:
+Once a test is fixed, you continue where you left off using ``--start-at`` option:
 
 .. code-block:: bash