Add description of final state: geo not enabled

doc/gitlab-geo/disaster-recovery.md

-# Disaster Recovery
+# GitLab Geo Disaster Recovery
 
 > **Note:** Disaster Recovery is in **Alpha** development. Do not use this as
 > your only Disaster Recovery strategy as you may lose data.
@@ -17,6 +17,9 @@ See [current limitations](README.md#current-limitations) for more information.
 We don't provide yet an automated way to promote a node and do fail-over,
 but you can do it manually if you have `root` access to the machine.
 
+This process promotes a secondary node to a primary node by the shortest path.
+It does not enable GitLab Geo on the newly promoted primary.
+
 1. Take down your **primary** node.
 
     SSH into your primary node and stop GitLab.
@@ -40,14 +43,14 @@ but you can do it manually if you have `root` access to the machine.
     sudo -i
     ```
 
-1. Optional. Update the DNS records and the `external_url`.
+1. Optional. Update the primary domains DNS record.
     
     Updating the DNS records for the primary domain to point to the secondary
     node will prevent the need to update all references to the primary domain
     to the secondary domain, like changing Git remotes and API URLs.
 
-    After updating the DNS records, edit `/etc/gitlab/gitlab.rb` to reflect the
-    new URL:
+    After updating the primary domains DNS records to point to the secondary,
+    edit `/etc/gitlab/gitlab.rb` on the the secondary to reflect the new URL:
 
     ```
     # Change the existing external_url configuration
@@ -63,13 +66,6 @@ but you can do it manually if you have `root` access to the machine.
     geo_secondary_role['enable'] = true
     ```
 
-    Add the following line:
-
-    ```
-    ## ADD THIS LINE
-    geo_primary_role['enable'] = true
-    ```
-
     A new secondary should not be added at this time. If you want to add a new
     secondary, do this after you have completed the entire process of promoting
     the secondary node to the primary node.
@@ -87,6 +83,10 @@ but you can do it manually if you have `root` access to the machine.
     If you updated the DNS records for the primary domain, these changes may
     not have yet propogated depending on the previous DNS records TTL.
 
-To bring your old primary node back into use as a working secondary, you need to
-run `gitlab-ctl reconfigure` against the node and then follow the
-[setup instructions](README.md) again, as if for a secondary node, from step 3.
+## Add secondary nodes to a promoted primary
+
+Promoting a secondary node to primary using the process above does not enable
+GitLab Geo on the new primary.
+
+To bring a new secondary node online, follow the [GitLab Geo setup
+instructions](README.md#setup-instructions).