summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarcel Amirault <mamirault@gitlab.com>2019-09-02 16:02:14 +0900
committerMarcel Amirault <mamirault@gitlab.com>2019-09-02 16:53:47 +0900
commit54b229622ae0edf27e898fd3d49fe97f08842d3a (patch)
tree18c5331616920ebfbfe257440bbf6ada6ecc74c1
parentf891065e8ce190f119e132ad8885931af85ae707 (diff)
downloadgitlab-ce-docs-james-gill-contribution.tar.gz
-rw-r--r--doc/administration/geo/replication/updating_the_geo_nodes.md2
-rw-r--r--doc/development/documentation/index.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/administration/geo/replication/updating_the_geo_nodes.md b/doc/administration/geo/replication/updating_the_geo_nodes.md
index 4d678030531..8c27c4dac4f 100644
--- a/doc/administration/geo/replication/updating_the_geo_nodes.md
+++ b/doc/administration/geo/replication/updating_the_geo_nodes.md
@@ -6,7 +6,7 @@ Depending on which version of Geo you are updating to/from, there may be differe
NOTE: **Note:** These general update steps are not intended for [high-availability deployments](https://docs.gitlab.com/omnibus/update/README.html#multi-node--ha-deployment), and will cause downtime. If you want to avoid downtime, consider using [zero downtime updates](https://docs.gitlab.com/omnibus/update/README.html#zero-downtime-updates).
-To update the Geo nodes when a new GitLab version is released, update **primary**
+To update the Geo nodes when a new GitLab version is released, update **primary**
and all **secondary** nodes:
1. Log into the **primary** node.
diff --git a/doc/development/documentation/index.md b/doc/development/documentation/index.md
index d98c56d27db..719b9aa212a 100644
--- a/doc/development/documentation/index.md
+++ b/doc/development/documentation/index.md
@@ -481,7 +481,7 @@ The current tests are:
### Linting
-To help adhere to the [documentation style guidelines](styleguide.md) and improve the content
+To help adhere to the [documentation style guidelines](styleguide.md), and improve the content
added to documentation, consider locally installing and running documentation linters. This will
help you catch common issues before raising merge requests for review of documentation.