summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLucas Charles <me@lucascharles.me>2019-06-05 14:49:52 +0000
committerLucas Charles <me@lucascharles.me>2019-06-05 14:49:52 +0000
commit10f5f536ae5ccb047d69080be5dae3bef0bb4f9f (patch)
treec6c0c1f96de4bb17c3c5220fa04a6f8e16028221
parent422fa21d0a7a4f7dd36ccb42e484c721398558b0 (diff)
downloadgitlab-ce-docs/patch-67.tar.gz
Update PROCESS.md - fix grammarpatch-67docs/patch-67
-rw-r--r--PROCESS.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/PROCESS.md b/PROCESS.md
index 1f99cebe081..3c40f658070 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -113,7 +113,7 @@ corresponding exception request to be created.
A level of common sense should be applied when deciding whether to have a feature
behind a feature flag off or on by default.
-The following guideliness can be applied to help make this decision:
+The following guidelines can be applied to help make this decision:
* If the feature is not fully ready or functioning, the feature flag should be disabled by default.
* If the feature is ready but there are concerns about performance or impact, the feature flag should be enabled by default, but
@@ -125,7 +125,7 @@ For more information on rolling out changes using feature flags, read [through t
In order to build the final package and present the feature for self-hosted
customers, the feature flag should be removed. This should happen before the
22nd, ideally _at least_ 2 days before. That means MRs with feature
-flags being picked at the 19th would have a quite tight schedule, so picking
+flags being picked at the 19th would have quite a tight schedule, so picking
these _earlier_ is preferable.
While rare, release managers may decide to reject picking a change into a stable