Update Edits

Signed-off-by: drew ogryzek <drew@drewbro.com>
This commit is contained in:
drew ogryzek 2016-04-28 16:15:47 -07:00
parent 354a71b4cf
commit d2c9f8bc9a
2 changed files with 4 additions and 4 deletions

View File

@ -37,7 +37,7 @@ shows the appliation's high level architecture:
![](../images/app-architecture.png)
All the servers are running Docker Engine. The entire application is fully
"dockerized" in that all services are running inside of containers.
"Dockerized" in that all services are running inside of containers.
The frontend consists of a load balancer with *N* frontend instances. Each
frontend consists of a web server and a Redis queue. The load balancer can
@ -56,7 +56,7 @@ Behind the frontend is a worker tier which runs on separate nodes. This tier:
Just like the frontend, the worker tier can also scale arbitrarily. The worker
count and frontend count are independent from each other.
The application's dockerized microservices are deployed to a container network.
The application's Dockerized microservices are deployed to a container network.
Container networks are a feature of Docker Engine that allows communication
between multiple containers across multiple Docker hosts.

View File

@ -14,7 +14,7 @@ weight=-80
You've [deployed the load balancer, the discovery backend, and a Swarm
cluster](deploy-infra.md) so now you can build and deploy the voting application
itself. You do this by starting a number of "dockerized applications" running in
itself. You do this by starting a number of "Dockerized applications" running in
containers.
The diagram below shows the final application configuration including the overlay
@ -139,7 +139,7 @@ command below, look for the value constraint.
--name results-app docker/example-voting-app-result-app
```
7. Start the voting application twice. Once on each frontend node.
7. Start the voting application twice; once on each frontend node.
```bash
$ docker -H $(docker-machine ip manager):3376 run -t -d \