Remove redundant documented steps for Geo Setup

doc/gitlab-geo/README.md

@@ -3,7 +3,8 @@
 > **Notes:**
 - GitLab Geo is part of [GitLab Enterprise Edition Premium][ee].
 - Introduced in GitLab Enterprise Edition 8.9.
-  We recommend you use it with at least GitLab Enterprise Edition 8.14.
+  We recommend you use it with at least GitLab Enterprise Edition 8.14 for
+  basic Geo features, or latest version for a better experience.
 - You should make sure that all nodes run the same GitLab version.
 
 GitLab Geo allows you to replicate your GitLab instance to other geographical

doc/gitlab-geo/configuration.md

@@ -137,18 +137,6 @@ sensitive data in the database. Any secondary node must have the
     sudo -i
     ```
 
-1. Edit `/etc/gitlab/gitlab.rb`:
-
-    ```
-    geo_postgresql['enable'] = true
-    ```
-
-1. Reconfigure GitLab:
-
-    ```
-    sudo gitlab-ctl reconfigure
-    ```
-
 1. Get the contents of `id_rsa.pub` key that was pre-generated by Omnibus GitLab
    and copy them:
 

doc/gitlab-geo/database.md

@@ -171,6 +171,7 @@ The following guide assumes that:
 
     ```ruby
     geo_secondary_role['enable'] = true
+    geo_postgresql['enable'] = true
     ```
 
 1. [Reconfigure GitLab][] for the changes to take effect.