summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorArun Kumar Mohan <arunmohandm@gmail.com>2019-08-19 00:02:10 -0500
committerArun Kumar Mohan <arunmohandm@gmail.com>2019-08-19 00:02:10 -0500
commitf3184b226872b008158fbe3ad832c14e34dc67bc (patch)
tree8f595634a7c74b59a6239cb3ddd410591970276b
parentc7d12e602120bc0ec801b9696c7ac344dda10fc4 (diff)
downloadgitlab-ce-f3184b226872b008158fbe3ad832c14e34dc67bc.tar.gz
Fix minor typo: CE -> EE
-rw-r--r--doc/development/automatic_ce_ee_merge.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/automatic_ce_ee_merge.md b/doc/development/automatic_ce_ee_merge.md
index 98b8a48abf4..001a92790e1 100644
--- a/doc/development/automatic_ce_ee_merge.md
+++ b/doc/development/automatic_ce_ee_merge.md
@@ -200,7 +200,7 @@ code.
### Why merge automatically?
As we work towards continuous deployments and a single repository for both CE
-and EE, we need to first make sure that all CE changes make their way into CE as
+and EE, we need to first make sure that all CE changes make their way into EE as
fast as possible. Past experiences and data have shown that periodic CE to EE
merge requests do not scale, and often take a very long time to complete. For
example, [in this