Merge branch 'jramsay-4089-ssh-authorization-docs' into 'master'

Add next step link to ssh authorization geo step

Closes #4089

See merge request gitlab-org/gitlab-ee!3459

doc/gitlab-geo/database.md

@@ -455,9 +455,10 @@ instructions for [enabling tracking database on the secondary server][tracking].
 
 ### Next steps
 
-Now that the database replication is done, the next step is to configure GitLab.
+Now that the database replication is done, the next step is to configure SSH
+authorizations to use the database.
 
-[➤ GitLab Geo configuration](configuration.md)
+[➤ Configure SSH authorizations to use the database](ssh.md)
 
 ## MySQL replication
 

doc/gitlab-geo/database_source.md

@@ -451,9 +451,10 @@ The replication process is now over.
 
 ### Next steps
 
-Now that the database replication is done, the next step is to configure GitLab.
+Now that the database replication is done, the next step is to configure SSH
+authorizations to use the database.
 
-[➤ GitLab Geo configuration](configuration_source.md)
+[➤ Configure SSH authorizations to use the database](ssh.md)
 
 ## MySQL replication
 

doc/gitlab-geo/ssh.md

@@ -21,3 +21,14 @@ lookups](../administration/operations/speed_up_ssh.html).
 Note that the 'Write to "authorized keys" file' checkbox only needs
 to be unchecked on the primary node since it will be reflected automatically
 in the secondary if database replication is working.
+
+### Next steps
+
+Now that SSH authorizations are configured to use the database, the next step
+is to configure GitLab.
+
+[➤ GitLab Geo configuration](configuration.md)
+
+If you are running GitLab installed from source:
+
+[➤ GitLab Geo configuration (source)](configuration_source.md)