summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNikolay Samokhvalov <gitlab@samokhvalov.com>2019-07-22 15:32:38 +0000
committerNikolay Samokhvalov <gitlab@samokhvalov.com>2019-07-22 15:32:38 +0000
commitdc2267b37da17fa04f2545e36f86f5627c1604fd (patch)
treea7e2aa16eec092c51192fd95f759a8e344badaf4
parent82744a31923f14062a230310a2004edf2b16e34c (diff)
downloadgitlab-ce-dc2267b37da17fa04f2545e36f86f5627c1604fd.tar.gz
Apply suggestion to doc/development/migration_style_guide.md
-rw-r--r--doc/development/migration_style_guide.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/migration_style_guide.md b/doc/development/migration_style_guide.md
index 98c67a23bea..188032c3592 100644
--- a/doc/development/migration_style_guide.md
+++ b/doc/development/migration_style_guide.md
@@ -11,7 +11,7 @@ guide below.
Migrations are **not** allowed to require GitLab installations to be taken
offline unless _absolutely necessary_. Downtime assumptions should be based on
-the behavior of migration when performed using PostgreSQL, as various
+the behavior of the migration when performed using PostgreSQL, as various
operations in MySQL may require downtime without there being alternatives.
When downtime is necessary the migration has to be approved by: