Start splitting Omnibus and source installation Geo docs

[ci skip]

doc/gitlab-geo/README.md

@@ -7,19 +7,6 @@ We recommend you use with at least GitLab 8.6 EE.
 GitLab Geo allows you to replicate your GitLab instance to other geographical
 locations as a read-only fully operational version.
 
-- [Overview](#overview)
-- [Setup instructions](#setup-instructions)
-    - [Database Replication](database.md)
-    - [Configuration](configuration.md)
-- [Current limitations](#current-limitations)
-- [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)
-    - [Can I git push to a secondary node?](#can-i-git-push-to-a-secondary-node)
-    - [How long does it take to have a commit replicated to a secondary node?](#how-long-does-it-take-to-have-a-commit-replicated-to-a-secondary-node)
-    - [What happens if the SSH server runs at a different port?](#what-happens-if-the-ssh-server-runs-at-a-different-port)
-
 ## Overview
 
 If you have two or more teams geographically spread out, but your GitLab
@@ -70,8 +57,8 @@ there are a few things to consider:
          ```
 
 >**Important**:
-The initialization of a new Geo secondary node on versions older than 8.14 
-requires data to be copied from the primary, as there is no backfill 
+The initialization of a new Geo secondary node on versions older than 8.14
+requires data to be copied from the primary, as there is no backfill
 feature bundled with those versions.
 See more details in the [Configure GitLab](configuration.md) step.
 

doc/gitlab-geo/configuration.md

@@ -2,40 +2,17 @@
 
 This is the final step you need to follow in order to setup a Geo node.
 
----
-
-<!-- START doctoc generated TOC please keep comment here to allow auto update -->
-<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
-**Table of Contents**
-
-- [Setting up GitLab](#setting-up-gitlab)
-  - [Prerequisites](#prerequisites)
-  - [Step 1. Adding the primary GitLab node](#step-1-adding-the-primary-gitlab-node)
-  - [Step 2. Updating the `known_hosts` file of the secondary nodes](#step-2-updating-the-known_hosts-file-of-the-secondary-nodes)
-  - [Step 3. Copying the database encryption key](#step-3-copying-the-database-encryption-key)
-  - [Step 4. Enabling the secondary GitLab node](#step-4-enabling-the-secondary-gitlab-node)
-  - [Step 5. Replicating the repositories data](#step-5-replicating-the-repositories-data)
-  - [Step 6. Regenerating the authorized keys in the secondary node](#step-6-regenerating-the-authorized-keys-in-the-secondary-node)
-  - [Next steps](#next-steps)
-- [Adding another secondary Geo node](#adding-another-secondary-geo-node)
-- [Additional information for the SSH key pairs](#additional-information-for-the-ssh-key-pairs)
-- [Troubleshooting](#troubleshooting)
-
-<!-- END doctoc generated TOC please keep comment here to allow auto update -->
-
 ## Setting up GitLab
 
 >**Notes:**
 - Don't setup any custom authentication in the secondary nodes, this will be
   handled by the primary node.
 - Do not add anything in the secondaries Geo nodes admin area
-   (**Admin Area ➔ Geo Nodes**). This is handled solely by the primary node.
-
----
+  (**Admin Area ➔ Geo Nodes**). This is handled solely by the primary node.
 
 After having installed GitLab Enterprise Edition in the instance that will serve
-as a Geo node and set up the [database replication](database.md), the next steps can be summed
-up to:
+as a Geo node and set up the [database replication](database.md), the next steps
+can be summed up to:
 
 1. Configure the primary node
 1. Replicate some required configurations between the primary and the secondaries