diff --git a/examples/guestbook/README.md b/examples/guestbook/README.md index 2758512c991..8796c75318c 100644 --- a/examples/guestbook/README.md +++ b/examples/guestbook/README.md @@ -153,7 +153,7 @@ This will cause all pods to see the redis master apparently running on :6379 Thus, once created, the service proxy on each minion is configured to set up a proxy on the specified port (in this case port 6379). ### Step Three: Fire up the replicated slave pods -Although the redis master is a single pod, the redis read slaves are a 'replicated' pod. In Kubernetes, a replication controller is responsible for managing multiple instances of a replicated pod. The replicationController will automatically launch new Pods if the number of replicas falls (this is quite easy - and fun - to test, just kill the docker processes for your pods at will and watch them come back online on a new node shortly thereafter). +Although the redis master is a single pod, the redis read slaves are a 'replicated' pod. In Kubernetes, a replication controller is responsible for managing multiple instances of a replicated pod. The replication controller will automatically launch new pods if the number of replicas falls (this is quite easy - and fun - to test, just kill the docker processes for your pods at will and watch them come back online on a new node shortly thereafter). Use the file `examples/guestbook/redis-slave-controller.json`, which looks like this: