Typos and englishify user-guide

docs/user-guide/jobs/expansions/index.md

@@ -54,7 +54,7 @@ job-banana.yaml
 job-cherry.yaml
 ```
 
-Here, we used `sed` to replace the string `$ITEM` with the the loop variable.
+Here, we used `sed` to replace the string `$ITEM` with the loop variable.
 You could use any type of template language (jinja2, erb) or write a program
 to generate the Job objects.
 

docs/user-guide/jobs/work-queue-1/index.md

@@ -122,8 +122,7 @@ root@temp-loe07:/#
 ```
 
 In the last command, the `amqp-consume` tool takes one message (`-c 1`)
-from the queue, and passes that message to the standard input of an
-an arbitrary command.  In this case, the program `cat` is just printing
+from the queue, and passes that message to the standard input of an arbitrary command.  In this case, the program `cat` is just printing
 out what it gets on the standard input, and the echo is just to add a carriage
 return so the example is readable.
 
@@ -169,7 +168,7 @@ example program:
 
 {% include code.html language="python" file="worker.py" ghlink="/docs/user-guide/job/work-queue-1/worker.py" %}
 
-Now, build an an image.  If you are working in the source
+Now, build an image.  If you are working in the source
 tree, then change directory to `examples/job/work-queue-1`.
 Otherwise, make a temporary directory, change to it,
 download the [Dockerfile](Dockerfile?raw=true),
@@ -275,7 +274,7 @@ not all items will be processed.
 If the number of completions is set to more than the number of items in the queue,
 then the Job will not appear to be completed, even though all items in the queue
 have been processed.  It will start additional pods which will block waiting
-for a mesage.
+for a message.
 
 There is an unlikely race with this pattern.  If the container is killed in between the time
 that the message is acknowledged by the amqp-consume command and the time that the container

docs/user-guide/jobs/work-queue-2/index.md

@@ -31,7 +31,7 @@ Here is an overview of the steps in this example:
 
 For this example, for simplicitly, we will start a single instance of Redis.
 See the [Redis Example](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/redis/README.md) for an example
-of deploying Redis scaleably and redundantly.
+of deploying Redis scalably and redundantly.
 
 Start a temporary Pod running Redis and a service so we can find it.