made change to massively_scalable section

removed the which - didn’t make sense
removed extra to - didn’t make sense

Change-Id: I470d41fbbed61e7bd82d189b154f369c95d42c05
This commit is contained in:
Shilla Saebi 2014-12-12 02:48:18 -05:00
parent 356358e94f
commit 737432646f

View File

@ -45,7 +45,7 @@
minimal impact in smaller deployments could become pain points minimal impact in smaller deployments could become pain points
at massive scale. If the issue is well known, in many cases, at massive scale. If the issue is well known, in many cases,
it may be resolved in more recent releases. The OpenStack 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.</para> the collective expertise of the OpenStack developers.</para>
<para>When issues crop up, the number of organizations running at <para>When issues crop up, the number of organizations running at
a similar scale is a relatively tiny proportion of the a similar scale is a relatively tiny proportion of the
@ -63,7 +63,7 @@
underlying components required to resolve issues or gain underlying components required to resolve issues or gain
significant performance improvements. At first glance, this significant performance improvements. At first glance, this
could be perceived as potentially exposing the deployment to 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.</para> could be an issue that has not been discovered yet.</para>
<para>It is advisable to cultivate a development and operations <para>It is advisable to cultivate a development and operations
organization that is responsible for creating desired organization that is responsible for creating desired