From 30a08e5f96cdd893bc2be10ab1c639e8e293dbe4 Mon Sep 17 00:00:00 2001
From: Jessica <jessica.tomechak@citrix.com>
Date: Thu, 8 Aug 2013 21:52:34 -0700
Subject: [PATCH] CLOUDSTACK-816. DOC. Fix position of health check
 configuration step in adding a load balancer rule. Fix to document for health
 checks for load balanced instances.

---
 docs/en-US/add-load-balancer-rule.xml | 32 +++++++++++++--------------
 1 file changed, 16 insertions(+), 16 deletions(-)

diff --git a/docs/en-US/add-load-balancer-rule.xml b/docs/en-US/add-load-balancer-rule.xml
index b679736ba8b..ef3305e98e8 100644
--- a/docs/en-US/add-load-balancer-rule.xml
+++ b/docs/en-US/add-load-balancer-rule.xml
@@ -74,24 +74,24 @@
           <para><emphasis role="bold">AutoScale</emphasis>: Click Configure and complete the
             AutoScale configuration as explained in <xref linkend="autoscale"/>.</para>
         </listitem>
+        <listitem><para><emphasis role="bold">Health Check</emphasis>: (Optional; NetScaler load balancers only) Click
+          Configure and fill in the characteristics of the health check policy. See <xref
+            linkend="health-checks-for-lb-rules"/>.</para>		
+          <itemizedlist>
+            <listitem><para><emphasis role="bold">Ping path (Optional)</emphasis>: Sequence of destinations to which to send health check queries.
+              Default: / (all).</para></listitem>			
+            <listitem><para><emphasis role="bold">Response time (Optional)</emphasis>: How long to wait for a response from the health check (2 - 60 seconds).
+              Default: 5 seconds.</para></listitem>
+            <listitem><para><emphasis role="bold">Interval time (Optional)</emphasis>: Amount of time between health checks (1 second - 5 minutes).
+              Default value is set in the global configuration parameter lbrule_health check_time_interval.</para></listitem>
+            <listitem><para><emphasis role="bold">Healthy threshold (Optional)</emphasis>: Number of consecutive health check successes
+              that are required before declaring an instance healthy.
+              Default: 2.</para></listitem>
+            <listitem><para><emphasis role="bold">Unhealthy threshold (Optional)</emphasis>: Number of consecutive health check failures that are required before declaring an instance unhealthy. 
+              Default: 10.</para></listitem>     
+          </itemizedlist></listitem>
       </itemizedlist>
     </listitem>
-    <listitem><para><emphasis role="bold">Health Check</emphasis>: (Optional; NetScaler load balancers only) Click
-        Configure and fill in the characteristics of the health check policy. See <xref
-          linkend="health-checks-for-lb-rules"/>.</para>		
-      <itemizedlist>
-        <listitem><para><emphasis role="bold">Ping path (Optional)</emphasis>: Sequence of destinations to which to send health check queries.
-          Default: / (all).</para></listitem>			
-        <listitem><para><emphasis role="bold">Response time (Optional)</emphasis>: How long to wait for a response from the health check (2 - 60 seconds).
-          Default: 5 seconds.</para></listitem>
-        <listitem><para><emphasis role="bold">Interval time (Optional)</emphasis>: Amount of time between health checks (1 second - 5 minutes).
-          Default value is set in the global configuration parameter lbrule_health check_time_interval.</para></listitem>
-        <listitem><para><emphasis role="bold">Healthy threshold (Optional)</emphasis>: Number of consecutive health check successes
-          that are required before declaring an instance healthy.
-          Default: 2.</para></listitem>
-        <listitem><para><emphasis role="bold">Unhealthy threshold (Optional)</emphasis>: Number of consecutive health check failures that are required before declaring an instance unhealthy. 
-          Default: 10.</para></listitem>     
-      </itemizedlist></listitem>
     <listitem>
       <para>Click Add VMs, then select two or more VMs that will divide the load of incoming
         traffic, and click Apply.</para>