From 318e1a6f3baf5a0f409535c69756189153d1fe08 Mon Sep 17 00:00:00 2001 From: Scott Konzem Date: Fri, 5 Jun 2015 11:35:17 -0400 Subject: [PATCH] Fix misspellings in documentation --- celery-rabbitmq/README.md | 2 +- guestbook/README.md | 2 +- k8petstore/README.md | 2 +- meteor/README.md | 6 +++--- rethinkdb/README.md | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/celery-rabbitmq/README.md b/celery-rabbitmq/README.md index 288a1504..877c5d70 100644 --- a/celery-rabbitmq/README.md +++ b/celery-rabbitmq/README.md @@ -146,7 +146,7 @@ ENV C_FORCE_ROOT 1 CMD ["/bin/bash", "/usr/local/bin/run.sh"] ``` -The celery\_conf.py contains the defintion of a simple Celery task that adds two numbers. This last line starts the Celery worker. +The celery\_conf.py contains the definition of a simple Celery task that adds two numbers. This last line starts the Celery worker. **NOTE:** `ENV C_FORCE_ROOT 1` forces Celery to be run as the root user, which is *not* recommended in production! diff --git a/guestbook/README.md b/guestbook/README.md index fe5ff160..1cba5288 100644 --- a/guestbook/README.md +++ b/guestbook/README.md @@ -513,7 +513,7 @@ When you go to localhost:8000, you might not see the page at all. Testing it wi ```shell ==> default: curl: (56) Recv failure: Connection reset by peer ``` -This means the web frontend isn't up yet. Specifically, the "reset by peer" message is occuring because you are trying to access the *right port*, but *nothing is bound* to that port yet. Wait a while, possibly about 2 minutes or more, depending on your set up. Also, run a *watch* on docker ps, to see if containers are cycling on and off or not starting. +This means the web frontend isn't up yet. Specifically, the "reset by peer" message is occurring because you are trying to access the *right port*, but *nothing is bound* to that port yet. Wait a while, possibly about 2 minutes or more, depending on your set up. Also, run a *watch* on docker ps, to see if containers are cycling on and off or not starting. ```watch $> watch -n 1 docker ps diff --git a/k8petstore/README.md b/k8petstore/README.md index aba63da4..631b42b3 100644 --- a/k8petstore/README.md +++ b/k8petstore/README.md @@ -14,7 +14,7 @@ If you are new to kubernetes, and you haven't run guestbook yet, you might want to stop here and go back and run guestbook app first. -The guestbook tutorial will teach you alot about the basics of kubernetes, and we've tried not to be redundant here. +The guestbook tutorial will teach you a lot about the basics of kubernetes, and we've tried not to be redundant here. ## Architecture of this SOA diff --git a/meteor/README.md b/meteor/README.md index ad08de30..f2b1ca3f 100644 --- a/meteor/README.md +++ b/meteor/README.md @@ -69,9 +69,9 @@ your cluster. Edit [`meteor-controller.json`](meteor-controller.json) and make s points to the container you just pushed to the Docker Hub or GCR. As you may know, Meteor uses MongoDB, and we'll need to provide it a -persistant Kuberetes volume to store its data. See the [volumes +persistent Kuberetes volume to store its data. See the [volumes documentation](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/volumes.md) -for options. We're going to use Google Compute Engine persistant +for options. We're going to use Google Compute Engine persistent disks. Create the MongoDB disk by running: ``` gcloud compute disks create --size=200GB mongo-disk @@ -140,7 +140,7 @@ documentation](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/doc for more information. As mentioned above, the mongo container uses a volume which is mapped -to a persistant disk by Kubernetes. In [`mongo-pod.json`](mongo-pod.json) the container +to a persistent disk by Kubernetes. In [`mongo-pod.json`](mongo-pod.json) the container section specifies the volume: ``` "volumeMounts": [ diff --git a/rethinkdb/README.md b/rethinkdb/README.md index c3e9a4fa..ca99d3f3 100644 --- a/rethinkdb/README.md +++ b/rethinkdb/README.md @@ -80,7 +80,7 @@ rethinkdb-rc-1.16.0-manu6 Admin ----- -You need a separate pod (which labled as role:admin) to access Web Admin UI +You need a separate pod (labeled as role:admin) to access Web Admin UI ```shell kubectl create -f admin-pod.yaml