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.</para>
     <para>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.</para>
     <para>It is advisable to cultivate a development and operations
         organization that is responsible for creating desired