summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFabio Busatto (OOO until 19/3) <fabio@gitlab.com>2018-03-12 15:13:14 +0000
committerbikebilly <fabio@gitlab.com>2018-06-18 08:44:15 -0400
commitbd0f9cd61c6daedf84eaef88e82572000c6eabfc (patch)
tree2a1bec187013a57f205b30f1e1215e17c72b3e96
parenta0e5c299e371ada2ff0229e09dbb002f51970794 (diff)
downloadgitlab-ce-bd0f9cd61c6daedf84eaef88e82572000c6eabfc.tar.gz
Copyedit
-rw-r--r--PROCESS.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/PROCESS.md b/PROCESS.md
index 29e66284989..bf9e4b203c7 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -239,7 +239,7 @@ available in the package repositories.
### How to manage a regression
Regressions are very important, and they should be considered high priority
-issues that should be solved as soon as possible, expecially if they affect
+issues that should be solved as soon as possible, especially if they affect
users. Anyway, ~regression label itself is not a [priority label].
When a regression is found: