summaryrefslogtreecommitdiff
path: root/doc/development
diff options
context:
space:
mode:
authorTakuya Noguchi <takninnovationresearch@gmail.com>2017-12-03 13:03:45 +0900
committerTakuya Noguchi <takninnovationresearch@gmail.com>2017-12-03 13:07:41 +0900
commit0f99e9a50b3faf1da47d37a0642d22e636498a80 (patch)
treef0a9679722a82b0e92264ceac8ed318172dfd9f1 /doc/development
parente0f84130567dc34edf1ae75fcf595e24991d2fa9 (diff)
downloadgitlab-ce-0f99e9a50b3faf1da47d37a0642d22e636498a80.tar.gz
Fix typo in docs about Elasticsearch
Diffstat (limited to 'doc/development')
-rw-r--r--doc/development/changelog.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/changelog.md b/doc/development/changelog.md
index f869938fe11..48cffc0dd18 100644
--- a/doc/development/changelog.md
+++ b/doc/development/changelog.md
@@ -80,7 +80,7 @@ changes.
The first example focuses on _how_ we fixed something, not on _what_ it fixes.
The rewritten version clearly describes the _end benefit_ to the user (fewer 500
-errors), and _when_ (searching commits with ElasticSearch).
+errors), and _when_ (searching commits with Elasticsearch).
Use your best judgement and try to put yourself in the mindset of someone
reading the compiled changelog. Does this entry add value? Does it offer context