diff --git a/README.md b/README.md
index c2a9857..ead5586 100644
--- a/README.md
+++ b/README.md
@@ -61,22 +61,15 @@ The SDK is not available for Linux at the moment. To get started on Linux, see o
Important! Emscripten is very specific about the versions of Clang it supports! Currently Clang 3.2 is being used, building a newer version can have some issues!
-## SDK Concepts
+## Getting Started with Emscripten
-The Emscripten SDK is effectively a small package manager for tools that are used in conjunction with Emscripten. The following glossary highlights the important concepts to help understanding the internals of the SDK:
-
-* Tool: The basic unit of software bundled in the SDK. A Tool has a name and a version. For example, 'clang-3.2-32bit' is a Tool that contains the 32-bit version of the Clang v3.2 compiler.
-* SDK: A set of tools. For example, 'sdk-1.5.6-32bit' is an SDK consisting of the tools clang-3.2-32bit, node-0.10.17-32bit, python-2.7.5.1-32bit and emscripten-1.5.6.
-* Active Tool/SDK: Emscripten stores compiler configuration in a user-specific file ~/.emscripten. This file points to paths for Emscripten, Python, Clang and so on. If the file ~/.emscripten is configured to point to a Tool in a specific directory, then that tool is denoted as being active. The Emscripten Command Prompt always gives access to the currently active Tools. This mechanism allows switching between different SDK versions easily.
-* emsdk: This is the name of the manager script that Emscripten SDK is accessed through. Most operations are of the form `emsdk command`. To access the emsdk script, launch the Emscripten Command Prompt.
-
-## Using the SDK
-
-The tools in the Emscripten SDK can be accessed in various ways. Which one you use depends on your preference. See the Emscripten [Tutorial](https://github.com/kripken/emscripten/wiki/Tutorial) page for help on
+The tools in the Emscripten toolchain can be accessed in various ways. Which one you use depends on your preference.
##### Command line usage
-The Emscripten compiler is available on the command line in the folder `emsdk/emscripten//` by invoking `emcc` or `em++`. You can add this directory to PATH to get an easy access to the toolchain.
+The Emscripten compiler is available on the command line by invoking `emcc` or `em++`. They are located in the folder `emsdk/emscripten//` in the SDK. You can add this directory to PATH to get an easy access to the toolchain.
+
+Check out the tutorial! See the Emscripten [Tutorial](https://github.com/kripken/emscripten/wiki/Tutorial) page for help on how to get going with the tools from command line.
##### Windows: Emscripten Command Prompt
@@ -86,6 +79,15 @@ Start the Emscripten Command Prompt from Start Menu -> All Programs -> Emscripte
After installing the vs-tool plugin, a new 'Emscripten' configuration will appear to the list of all Solution Configurations in Visual Studio. Activating that configuration for a solution/project will make Visual Studio run the project build through Emscripten, producing .html or .js output, depending on the project properties you set up.
+## SDK Concepts
+
+The Emscripten SDK is effectively a small package manager for tools that are used in conjunction with Emscripten. The following glossary highlights the important concepts to help understanding the internals of the SDK:
+
+* Tool: The basic unit of software bundled in the SDK. A Tool has a name and a version. For example, 'clang-3.2-32bit' is a Tool that contains the 32-bit version of the Clang v3.2 compiler.
+* SDK: A set of tools. For example, 'sdk-1.5.6-32bit' is an SDK consisting of the tools clang-3.2-32bit, node-0.10.17-32bit, python-2.7.5.1-32bit and emscripten-1.5.6.
+* Active Tool/SDK: Emscripten stores compiler configuration in a user-specific file ~/.emscripten. This file points to paths for Emscripten, Python, Clang and so on. If the file ~/.emscripten is configured to point to a Tool in a specific directory, then that tool is denoted as being active. The Emscripten Command Prompt always gives access to the currently active Tools. This mechanism allows switching between different SDK versions easily.
+* emsdk: This is the name of the manager script that Emscripten SDK is accessed through. Most operations are of the form `emsdk command`. To access the emsdk script, launch the Emscripten Command Prompt.
+
## SDK Maintenance
The following tasks are common with the Emscripten SDK:
@@ -119,7 +121,7 @@ You can toggle between different tools and SDK versions by running `emsdk activa
## Uninstalling the Emscripten SDK
-If you installed the SDK using a NSIS installer, launch 'Control Panel' -> 'Uninstall a program' -> 'Emscripten SDK'.
+If you installed the SDK using a NSIS installer on Windows, launch 'Control Panel' -> 'Uninstall a program' -> 'Emscripten SDK'.
If you want to remove a Portable SDK, just delete the directory where you put the Portable SDK into.