summaryrefslogtreecommitdiff
path: root/doc/update
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2021-05-18 18:10:54 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2021-05-18 18:10:54 +0000
commit042cd704b8177e7997af4a2ca90967d3178ccc3f (patch)
tree06fec320acf76fbb87df66810cd75fe4e7f2357c /doc/update
parent346c2ebb5a818524c5d8d95dc6b9fc8c892e3b5c (diff)
downloadgitlab-ce-042cd704b8177e7997af4a2ca90967d3178ccc3f.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/update')
-rw-r--r--doc/update/index.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/update/index.md b/doc/update/index.md
index 5c6f47d2b9c..4c4dfe79d03 100644
--- a/doc/update/index.md
+++ b/doc/update/index.md
@@ -148,7 +148,7 @@ If you upgrade your GitLab instance while the GitLab Runner is processing jobs,
As for the artifacts, the GitLab Runner will attempt to upload them three times, after which the job will eventually fail.
-To address the above two scenario's, it is adviced to do the following prior to upgrading:
+To address the above two scenario's, it is advised to do the following prior to upgrading:
1. Plan your maintenance.
1. Pause your runners.