Fix internal link to Geo documentation

doc/gitlab-geo/README.md

@@ -9,10 +9,10 @@ locations as a read-only fully operational version.
 
 - [Overview](#overview)
 - [Setup instructions](#setup-instructions)
-    - [Database Replication](./database.md)
-    - [Configuration](./configuration.md)
+    - [Database Replication](database.md)
+    - [Configuration](configuration.md)
 - [Current limitations](#current-limitations)
-- [Disaster Recovery](./disaster-recovery.md)
+- [Disaster Recovery](disaster-recovery.md)
 - [Frequently Asked Questions](#frequently-asked-questions)
     - [Can I use Geo in a disaster recovery situation?](#can-i-use-geo-in-a-disaster-recovery-situation)
     - [What data is replicated to a secondary node?](#what-data-is-replicated-to-a-secondary-node)
@@ -53,7 +53,7 @@ Geo instances. Follow the steps below in the order that they appear:
 
 1. Install GitLab Enterprise Edition on the server that will serve as the
    secondary Geo node
-1. [Setup a database replication](./database.md) in `primary <-> secondary (read-only)` topology
+1. [Setup a database replication](database.md) in `primary <-> secondary (read-only)` topology
 1. [Configure GitLab](configuration.md) and set the primary and secondary nodes
 After you set up the database replication and configure the GitLab Geo nodes,
 there are a few things to consider:
@@ -79,7 +79,7 @@ In an extreme data-loss situation you can make a secondary Geo into your
 primary, but this is not officially supported yet.
 
 If you still want to proceed, see our step-by-step instructions on how to 
-manually [promote a secondary node](./disaster-recovery.md) into primary. 
+manually [promote a secondary node](disaster-recovery.md) into primary. 
 
 ### What data is replicated to a secondary node?
 

doc/gitlab-geo/configuration.md

 # GitLab Geo configuration
 
 By now, you should have an [idea of GitLab Geo](README.md) and already set up
-the [database replication](./database.md). There are a few more steps needed to
+the [database replication](database.md). There are a few more steps needed to
 complete the process.
 
 ---
@@ -84,7 +84,7 @@ Host example.com                    # The FQDN of the primary Geo node
 >**Note:**
 You will need to setup your database into a **Primary <-> Secondary (read-only)** replication
 topology, and your Primary node should always point to a database's Primary
-instance. If you haven't done that already, read [database replication](./database.md).
+instance. If you haven't done that already, read [database replication](database.md).
 
 Go to the server that you chose to be your primary, and visit
 **Admin Area > Geo Nodes** (`/admin/geo_nodes`) in order to add the Geo nodes.
@@ -116,7 +116,7 @@ up the secondary servers. This is handled by the primary server setup.
 To install a secondary node, you must follow the normal GitLab Enterprise
 Edition installation, with some extra requirements:
 
-- You should point your database connection to a [replicated instance](./database.md).
+- You should point your database connection to a [replicated instance](database.md).
 - Your secondary node should be allowed to communicate via HTTP/HTTPS and
   SSH with your primary node (make sure your firewall is not blocking that).
 
@@ -137,7 +137,7 @@ For Source installations it is stored at `/home/git/gitlab/config/secrets.yml`.
 The final step will be to regenerate the keys for `.ssh/authorized_keys` using
 the following command (HTTPS clone will still work without this extra step).
 
-On the secondary node where the database is [already replicated](./database.md),
+On the secondary node where the database is [already replicated](database.md),
 run the following:
 
 ```

doc/gitlab-geo/disaster-recovery.md

@@ -8,7 +8,7 @@ GitLab Geo replicates your database and your Git repositories. We will
 support and replicate more data in the future, that will enable you to
 fail-over with minimal effort, in a disaster situation. 
 
-See [current limitations](./README.md#current-limitations) 
+See [current limitations](README.md#current-limitations) 
 for more information.