few small spelling mistakes.

Author: Dave Conway-Jones

docs/getting-started/aws.md

@@ -12,7 +12,7 @@ This guide takes you through the steps to get Node-RED running in an AWS environ
 There are two approaches:
 
 1. [Running on the AWS Elastic Beanstalk Service (EB)](#running-on-aws-ebs)
-2. [Running on Elastic Beanstalk with High Availability](#running-on-elastic-beanstalk-with-high-availabilty)
+2. [Running on Elastic Beanstalk with High Availability](#running-on-elastic-beanstalk-with-high-availability)
 3. [Running under an Ubuntu image on AWS EC2](#running-on-aws-ec2-with-ubuntu)
 
 ### Running on AWS EBS
@@ -89,17 +89,17 @@ Node-RED is now accessible directly from the web url of the application. However
 
 2. Select the EC2 instance which is running the node-red application. copy its IP address
 
-3. Enter the IP address in the browser with a port of 8081. This will provide direct access to the node-red adminstration console.
+3. Enter the IP address in the browser with a port of 8081. This will provide direct access to the node-red administration console.
 
 Note: the public IP address also provides access to the node-red application and it would be good practice to remove that access at the same time  i.e. the HTTP rule for port 80.
 
 Your Node-RED instance is now running on EBS. Any flows you create will be saved to AWS S3 so you can tear down the environment and the flows will be accessible whenever you redeploy.
 
-### Running on Elastic Beanstalk with High Availabilty
+### Running on Elastic Beanstalk with High availability
 
 This deployment option gives you a multiple node Node-RED setup, with a shared filesystem using Amazon Elastic File System (EFS). Because it runs multiple nodes behind a load balancer, you will have high availabiliity - if a node dies, Elastic Beanstalk will replace it automgically.
 
-![solution diagram](/images/node-red-ha-on-aws.png "Node-RED on Elastic Beanstalk with High Availabilty")
+![solution diagram](/images/node-red-ha-on-aws.png "Node-RED on Elastic Beanstalk with High availability")
 
 To get started, clone the repository here [https://github.com/guysqr/node-red-ha-on-aws](https://github.com/guysqr/node-red-ha-on-aws) and follow the simple instructions. The infrastructure is created for you by a CloudFormation template, so you don't need to know much about AWS to set it up.
 

docs/getting-started/docker.md

@@ -223,7 +223,7 @@ Dockerfile
 README.md
 package.json     # add any extra nodes your flow needs into your own package.json.
 flows.json       # the normal place Node-RED store your flows
-flows_cred.json  # credemtials your flows may need
+flows_cred.json  # credentials your flows may need
 settings.js      # your settings file
 ```
 
@@ -278,7 +278,7 @@ You _build_ this Dockerfile normally:
 docker build -t your-image-name:your-tag .
 ```
 
-To _run_ locally for development where changes are written immediately and only the local directory that youre working from, `cd` into the project's directory and then run:
+To _run_ locally for development where changes are written immediately and only the local directory that you are working from, `cd` into the project's directory and then run:
 
 ```bash
 docker run --rm -e "NODE_RED_CREDENTIAL_SECRET=your_secret_goes_here" -p 1880:1880 -v `pwd`:/data --name a-container-name your-image-name
@@ -323,7 +323,7 @@ docker run -d -p 1880:1880 --name mynodered nodered/node-red
 Once it is running headless you can use the following command to get access back into the container.
 ```
 $ docker exec -it mynodered /bin/bash
-bash-4.4$ 
+bash-4.4$
 ```
 
 Will give a command line inside the container - where you can then run the npm install

docs/user-guide/context.md

@@ -133,6 +133,6 @@ The [Creating Nodes guide](/docs/creating-nodes/context) describes how to use co
 
 ### Deleting context from the file store
 
-Context can be permenantly deleted by using a Change node set to delete.
+Context can be permanently deleted by using a Change node set to delete.
 
 <div style="text-align: center"><img src="/docs/user-guide/images/context_delete.png" width="488px"></div>

docs/user-guide/editor/sidebar/info.md

@@ -20,7 +20,7 @@ title: 'Sidebar: Information'
 The Information sidebar shows information about the flows. This includes an outline
 view of all flows and nodes, as well as details of the current selection.
 
-The outline view can be searched using the same syntax as the [main seach dialog](../workspace/search).
+The outline view can be searched using the same syntax as the [main search dialog](../workspace/search).
 
 Hovering over an entry in the outline reveals a set of options.
 

docs/user-guide/writing-functions.md

@@ -174,7 +174,7 @@ if (context.get("counter") === undefined) {
 
 The Setup function can return a Promise if it needs to complete asynchronous work
 before the main Function can start processing messages. Any messages that arrive
-before the Setup function has completed will be queued up and handled when its ready.
+before the Setup function has completed will be queued up, and handled when it is ready.
 
 ### Tidying up