summaryrefslogtreecommitdiff
path: root/doc/operations
diff options
context:
space:
mode:
authorRobert Schilling <rschilling@student.tugraz.at>2015-10-31 23:31:21 +0100
committerRobert Schilling <rschilling@student.tugraz.at>2015-10-31 23:31:21 +0100
commita1d0eca88686faabd9742f92174a0caa76e36cf6 (patch)
treeb3f8aa9110a488c38482f5d44767b013a9f907f2 /doc/operations
parent1f8689693a9a850519821ec970b4810607004ea1 (diff)
downloadgitlab-ce-a1d0eca88686faabd9742f92174a0caa76e36cf6.tar.gz
Gilab -> GitLab
Diffstat (limited to 'doc/operations')
-rw-r--r--doc/operations/unicorn.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/operations/unicorn.md b/doc/operations/unicorn.md
index 31b432cd411..3998da01f01 100644
--- a/doc/operations/unicorn.md
+++ b/doc/operations/unicorn.md
@@ -78,7 +78,7 @@ threshold is a random value between 200 and 250 MB. The master process (PID
```
One other thing that stands out in the log snippet above, taken from
-Gitlab.com, is that 'worker 4' was serving requests for only 23 seconds. This
+GitLab.com, is that 'worker 4' was serving requests for only 23 seconds. This
is a normal value for our current GitLab.com setup and traffic.
The high frequency of Unicorn memory restarts on some GitLab sites can be a