Tidy up images and install/run docs

Author: knolleary

docs/getting-started/installation.md

@@ -10,25 +10,37 @@ You can get the latest version from <http://nodejs.org/download/>.
 Or, you may want to use a version from your operating system's package manager:
  <https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager>
 
-### Get Node-RED
+### Install Node-RED
 
-There are several ways to install Node-RED. The simplest is to use npm.
+There are two ways to get Node-RED; either via npm, or directly from GitHub:
 
+#### Using npm
+
+    $ mkdir node-red
+    $ cd node-red
     $ npm install node-red
 
-Or you can clone the repository from GitHub:
+This installs Node-RED, and its core dependencies into the `node_modules`
+directory.
 
-    $ git clone https://github.com/node-red/node-red.git
+Installing via npm also allows you to [embed Node-RED into an existing application](../embedding.html).
 
-Or you can download the latest zip file from <https://github.com/node-red/node-red/archive/master.zip>.
+The version installed by npm is a point-in-time snapshot. To get the latest code run:
 
-### Install the pre-requisite modules
+    $ npm install node-red/node-red
 
-From the top-level directory of Node-RED, run:
+#### From GitHub
 
-    $ npm install
+Either clone the repository:
+
+    $ git clone https://github.com/node-red/node-red.git
+
+Or download the latest zip file from <https://github.com/node-red/node-red/archive/master.zip>.
 
-This will install the core pre-requisite modules.
+Once downloaded, the core pre-requisite modules must be installed. From the top-level
+directory of Node-RED, run:
+
+    $ npm install
 
 ### Installing individual node dependencies
 
@@ -40,8 +52,9 @@ Each will have its own set of dependencies that will need to be installed before
 the node is available in the palette.
 
 To help identify the dependencies, Node-RED logs any modules it fails to find
-for a particular node. You don't have to install these unless you want or need
-that node to appear.
+for a particular node. You only need to install these dependencies if you want
+to use that node. For example, you probably don't want to install the `pi-gpio`
+module unless you are running on a Raspberry Pi.
 
 Alternatively, a node's `.js` file can be examined to identify the modules it
 explicitly requires. For example, the Twitter node is defined in

docs/getting-started/running.md

@@ -14,16 +14,17 @@ deployed configuration. You can point to a different flow file at start-up:
 
     $ node red.js my_flows.json
 
-You should now have a screen almost like this.
+
+### Editor UI
 
 ![ScreenShot][1]
 
   [1]: ../../images/node-red-screenshot2.png "ScreenShot"
 
 The key areas are
 
- 1. The Pallette on the left - Nodes can be dragged from here to the main canvas.
- 2. The Canvas or workarea - this is where you compose your flows.
- 3. The Information and Debug window - this can be accessed via the Option button top right, or by the shortcut ctrl-space.
- 4. The Deploy button - top right. This saves your flow and starts it running.
- 5. The Options button - top right. This gives access to other functions such as import/export and the debug window.
+ 1. The node palette - nodes can be dragged from here on to the main canvas.
+ 2. The canvas or workarea - this is where you compose your flows.
+ 3. The sidebar, including information and debug tabs - this can be accessed via the Options button top right, or pressing Ctrl-Space.
+ 4. The Deploy button - this saves your flow and starts it running. It turns red when there are undeployed changes.
+ 5. The Options menu - this gives access to other functions such as import/export and the sidebar.