summaryrefslogtreecommitdiff
path: root/doc/development/migration_style_guide.md
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axil@gitlab.com>2018-01-19 18:44:23 +0000
committerAchilleas Pipinellis <axil@gitlab.com>2018-01-19 18:44:23 +0000
commit9fb5bd416dbb9e7890a2befaa4145c3c8dde2431 (patch)
tree8837017470ee5f28642846a1cbd367fe3bf5b1f0 /doc/development/migration_style_guide.md
parent604c9133a75b235e3b537ad96dcf92ed6949ed65 (diff)
parent0cbbb08e790260ad936810e0047e03938c001e9b (diff)
downloadgitlab-ce-9fb5bd416dbb9e7890a2befaa4145c3c8dde2431.tar.gz
Merge branch 'spelling' into 'master'
doc: Spelling fixes See merge request gitlab-org/gitlab-ce!16575
Diffstat (limited 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 a235dd74909..243ac7f0c98 100644
--- a/doc/development/migration_style_guide.md
+++ b/doc/development/migration_style_guide.md
@@ -4,7 +4,7 @@ When writing migrations for GitLab, you have to take into account that
these will be ran by hundreds of thousands of organizations of all sizes, some with
many years of data in their database.
-In addition, having to take a server offline for a a upgrade small or big is a
+In addition, having to take a server offline for an upgrade small or big is a
big burden for most organizations. For this reason it is important that your
migrations are written carefully, can be applied online and adhere to the style
guide below.