From 6f46158ba35e137abebed70171c249386e6c85d0 Mon Sep 17 00:00:00 2001
From: Shilla Saebi <shilla.saebi@gmail.com>
Date: Sat, 6 Sep 2014 15:34:05 -0400
Subject: [PATCH] changes to section_run_openstack_api_and_schedulers

remove ) there is no (
remove space between Active/Passive
changed configure to configuring

Change-Id: I9396b03ca3e7d7c1b784dd068ecdd696624f74e1
---
 .../section_run_openstack_api_and_schedulers.xml            | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml b/doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml
index 1d2ccbe1ee..ed63a93886 100644
--- a/doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml
+++ b/doc/high-availability-guide/ha_aa_controllers/section_run_openstack_api_and_schedulers.xml
@@ -11,7 +11,7 @@
             <title>API services</title>
 
           <para>All OpenStack projects have an API service for controlling all the resources in the Cloud.
-In Active / Active mode, the most common setup is to scale-out these services on at least two nodes
+In active/active mode, the most common setup is to scale-out these services on at least two nodes
 and use load balancing and virtual IP (with HAProxy &amp; Keepalived in this setup).</para>
           <para>
             <emphasis role="strong">Configure API OpenStack services</emphasis>
@@ -33,7 +33,7 @@ All OpenStack configuration files should refer to virtual IPs.
             <emphasis role="strong">In case of failure</emphasis>
           </para>
           <para>The monitor check is quite simple since it just establishes a TCP connection to the API port. Comparing to the
-Active / Passive mode using Corosync &amp; Resources Agents, we don’t check if the service is actually running).
+active/passive mode using Corosync &amp; Resources Agents, we don’t check if the service is actually running.
 That’s why all OpenStack API should be monitored by another tool, for example Nagios, with the goal to detect
 failures in the Cloud Framework infrastructure.</para>
         </section>
@@ -76,6 +76,6 @@ heat-engine
 </para>
             </listitem>
           </itemizedlist>
-          <para>Please refer to the RabbitMQ section for configure these services with multiple messaging servers.</para>
+          <para>Please refer to the RabbitMQ section for configuring these services with multiple messaging servers.</para>
         </section>
       </section>