From 737432646fb8c89c69b64a3ab10135a671251e95 Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Fri, 12 Dec 2014 02:48:18 -0500 Subject: [PATCH] made change to massively_scalable section MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit removed the which - didn’t make sense removed extra to - didn’t make sense Change-Id: I470d41fbbed61e7bd82d189b154f369c95d42c05 --- .../section_operational_considerations_massively_scalable.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/arch-design/massively_scalable/section_operational_considerations_massively_scalable.xml b/doc/arch-design/massively_scalable/section_operational_considerations_massively_scalable.xml index 93d95d9f52..c999835b2d 100644 --- a/doc/arch-design/massively_scalable/section_operational_considerations_massively_scalable.xml +++ b/doc/arch-design/massively_scalable/section_operational_considerations_massively_scalable.xml @@ -45,7 +45,7 @@ minimal impact in smaller deployments could become pain points at massive scale. If the issue is well known, in many cases, it may be resolved in more recent releases. The OpenStack - community can help resolve any issues reported by the applying + community can help resolve any issues reported by applying the collective expertise of the OpenStack developers. When issues crop up, the number of organizations running at a similar scale is a relatively tiny proportion of the @@ -63,7 +63,7 @@ underlying components required to resolve issues or gain significant performance improvements. At first glance, this could be perceived as potentially exposing the deployment to - increased risk to and instability. However, in many cases it + increased risk and instability. However, in many cases it could be an issue that has not been discovered yet. It is advisable to cultivate a development and operations organization that is responsible for creating desired