diff --git a/docs/en-US/gslb.xml b/docs/en-US/gslb.xml
index 23033317381..8070e3055a5 100644
--- a/docs/en-US/gslb.xml
+++ b/docs/en-US/gslb.xml
@@ -157,29 +157,15 @@
   </section>
   <section id="gslb-workflow">
     <title>Configuring GSLB</title>
-    <para>A GSLB deployment is the logical collection of GSLB virtual server, GSLB service, LB
-      virtual server, service, domain, and ADNS service. To create a GSLB site, you must configure
-      load balancing in the zone. You must create GSLB vservers and GSLB services for each site. You
-      must bind GSLB services to GSLB vservers. You must then create an ADNS service that provides
-      the IP address of the best performing site to the client's request. A GSLB vserver is an
-      entity that performs load balancing for the domains bound to it by returning the IP address of
-      the best GSLB service. A GSLB service is a representation of the load balancing/content
-      switching vserver. An LB vserver load balances incoming traffic by identifying the best
-      server, then directs traffic to the corresponding service. It can also load-balance external
-      DNS name servers. Services are entities that represent the servers. The domain is the domain
-      name for which the system is the authoritative DNS server. By creating an ADNS service, the
-      system can be configured as an authoritative DNS server.</para>
-    <para>To configure GSLB in your cloud environment, as a cloud administrator you must perform the
-      following.</para>
-    <para>To configure such a GSLB setup, you must first configure a standard load balancing setup
+    <para>To configure a GSLB deployment, you must first configure a standard load balancing setup
       for each zone. This enables you to balance load across the different servers in each zone in
-      the region. Then, configure both NetScaler appliances that you plan to add to each zone as
-      authoritative DNS (ADNS) servers. Next, create a GSLB site for each zone, configure GSLB
-      virtual servers for each site, create GLSB services, and bind the GSLB services to the GSLB
-      virtual servers. Finally, bind the domain to the GSLB virtual servers. The GSLB configurations
-      on the two appliances at the two different sites are identical, although each sites
-      load-balancing configuration is specific to that site.</para>
-    <para>Perform the following as a cloud administrator. As per the above example, the
+      the region. Then on the NetScaler side, configure both NetScaler appliances that you plan to
+      add to each zone as authoritative DNS (ADNS) servers. Next, create a GSLB site for each zone,
+      configure GSLB virtual servers for each site, create GLSB services, and bind the GSLB services
+      to the GSLB virtual servers. Finally, bind the domain to the GSLB virtual servers. The GSLB
+      configurations on the two appliances at the two different zones are identical, although each
+      sites load-balancing configuration is specific to that site.</para>
+    <para>Perform the following as a cloud administrator. As per the example given above, the
       administrator of xyztelco is the one who sets up GSLB:</para>
     <orderedlist>
       <listitem>
@@ -200,7 +186,9 @@
                 >Configuring an Authoritative DNS Service</ulink>.</para>
           </listitem>
           <listitem>
-            <para>Configure a GSLB site with site name formed from the domain name details.</para>
+            <para>Configure a GSLB site with the site name formed from the domain name.</para>
+            <para>As per the example given above, the site names are A.xyztelco.com and
+              B.xyztelco.com.</para>
             <para>For more information, see <ulink
                 url="http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-basic-site-tsk.html"
                 >Configuring a Basic GSLB Site</ulink>.</para>
@@ -459,7 +447,6 @@
     </section>
     <section id="assign-lb-gslb">
       <title>Assigning Load Balancing Rules to GSLB</title>
-      <para/>
       <orderedlist>
         <listitem>
           <para>Log in to the &PRODUCT; UI as a domain administrator or user.</para>