[Geo Disaster recovery doc] fix links

doc/administration/geo/disaster_recovery/bring_primary_back.md

@@ -10,9 +10,9 @@ restore your original configuration. This process consists of two steps:
 
 ## Configure the former primary to be a secondary
 
-Since the former primary will be out of sync with the current primary, the first step is 
-to bring the former primary up to date. Note, deletion of data stored on disk like 
-repositories and uploads will not be replayed when bringing the former primary in back 
+Since the former primary will be out of sync with the current primary, the first step is
+to bring the former primary up to date. Note, deletion of data stored on disk like
+repositories and uploads will not be replayed when bringing the former primary in back
 into sync, which may result in increased disk usage.
 Alternatively, you can [setup a new secondary GitLab instance][setup-geo] to avoid this.
 
@@ -31,7 +31,7 @@ To bring the former primary up to date:
     the GitLab instance from scratch and setup it as a secondary node by
     following [Setup instructions][setup-geo].  In this case you don't need to follow the next step.
 
-    >**Note 2:** If you [changed the DNS records](disaster-recovery.md#step-4-optional-updating-the-primary-domains-dns-record)
+    >**Note 2:** If you [changed the DNS records](index.md#step-4-optional-updating-the-primary-domains-dns-record)
     for this node during disaster recovery procedure you may need to [block
     all the writes to this node](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/doc/gitlab-geo/planned-failover.md#block-primary-traffic)
     during this procedure.