summaryrefslogtreecommitdiff
path: root/doc/administration/geo
diff options
context:
space:
mode:
authorMarcel Amirault <mamirault@gitlab.com>2019-07-06 10:49:11 +0900
committerMarcel Amirault <mamirault@gitlab.com>2019-07-06 10:49:11 +0900
commit10753e4af955b2c9c2699f70b1f40e7e4268b355 (patch)
tree1e996a10d77dffd881b402c3262fd41294e95e12 /doc/administration/geo
parent05360776657830e7ea8f571de35163a7e904e8e3 (diff)
downloadgitlab-ce-docs-badge-refactor.tar.gz
More testing of kramdown warningsdocs-badge-refactor
Minor fixes to try to clean up warnings
Diffstat (limited to 'doc/administration/geo')
-rw-r--r--doc/administration/geo/replication/configuration.md2
-rw-r--r--doc/administration/geo/replication/updating_the_geo_nodes.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/administration/geo/replication/configuration.md b/doc/administration/geo/replication/configuration.md
index 0e11dffa0d6..f942c5e664a 100644
--- a/doc/administration/geo/replication/configuration.md
+++ b/doc/administration/geo/replication/configuration.md
@@ -242,7 +242,7 @@ node's Geo Nodes dashboard in your browser.
![Geo dashboard](img/geo_node_dashboard.png)
If your installation isn't working properly, check the
-[troubleshooting document].
+[troubleshooting document](troubleshooting.md).
The two most obvious issues that can become apparent in the dashboard are:
diff --git a/doc/administration/geo/replication/updating_the_geo_nodes.md b/doc/administration/geo/replication/updating_the_geo_nodes.md
index c27f6c78455..6107763ff30 100644
--- a/doc/administration/geo/replication/updating_the_geo_nodes.md
+++ b/doc/administration/geo/replication/updating_the_geo_nodes.md
@@ -241,7 +241,7 @@ Omnibus is the following:
1. Check the steps about defining `postgresql['sql_user_password']`, `gitlab_rails['db_password']`.
1. Make sure `postgresql['max_replication_slots']` matches the number of **secondary** Geo nodes locations.
1. Install GitLab on the **secondary** server.
-1. Re-run the [database replication process][database-replication].
+1. Re-run the [database replication process](database.md#step-3-initiate-the-replication-process).
## Special update notes for 9.0.x