summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorernstvn <ernst@gitlab.com>2017-06-08 10:56:29 -0700
committerernstvn <ernst@gitlab.com>2017-06-08 10:56:29 -0700
commit09f1530f84e2c738199967c5553cf581d8203dfc (patch)
tree5754faa09e736c424f8335840234df691a88120a /doc
parentee828f2947e69d37a4c239f83bf49b96df59ecf1 (diff)
downloadgitlab-ce-09f1530f84e2c738199967c5553cf581d8203dfc.tar.gz
Update per discussionevn-no-geo-either
Diffstat (limited to 'doc')
-rw-r--r--doc/install/requirements.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/install/requirements.md b/doc/install/requirements.md
index c25776c0adb..197a92905c8 100644
--- a/doc/install/requirements.md
+++ b/doc/install/requirements.md
@@ -129,7 +129,7 @@ We _highly_ recommend the use of PostgreSQL instead of MySQL/MariaDB as not all
features of GitLab may work with MySQL/MariaDB. For example, MySQL does not have
the right features to support nested groups in an efficient manner; see
<https://gitlab.com/gitlab-org/gitlab-ce/issues/30472> for more information
-about this. In GitLab Geo, MySQL replication is also [not supported](https://docs.gitlab.com/ee/gitlab-geo/database.html#mysql-replication).
+about this. GitLab Geo also does [not support MySQL](https://docs.gitlab.com/ee/gitlab-geo/database.html#mysql-replication).
Existing users using GitLab with MySQL/MariaDB are advised to
migrate to PostgreSQL instead.