From 7212d38bf66b1920ffe9d4d8dc6e49ea5bc121db Mon Sep 17 00:00:00 2001 From: Andreas Jaeger Date: Sun, 16 Mar 2014 19:19:29 +0100 Subject: [PATCH] Copy-edits for part_architecture This addresses just the edits, not the two notes. Change-Id: Id6c5da408adcb1e05bd7a28dd84e9ac1ee74840b --- doc/openstack-ops/part_architecture.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/openstack-ops/part_architecture.xml b/doc/openstack-ops/part_architecture.xml index 2e4008ac..c91431fa 100644 --- a/doc/openstack-ops/part_architecture.xml +++ b/doc/openstack-ops/part_architecture.xml @@ -14,11 +14,11 @@ Designing an OpenStack cloud is a great achievement. It requires a - robust understanding of the requirements and needs of the cloud + robust understanding of the requirements and needs of the cloud's users to determine the best possible configuration to meet them. OpenStack provides a great deal of flexibility to achieve your needs, and this part of the book aims to shine light on many of the - decisions you will need to make during the process. + decisions you need to make during the process. To design, deploy, and configure OpenStack, administrators must understand the logical architecture. A diagram can help @@ -43,7 +43,7 @@ Identity Service and individual services interact with each other through public APIs, except where privileged administrator commands are necessary. The diagram shows the - most common, but not the only, logical architecture for an + most common, but not the only logical architecture for an OpenStack cloud.