summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorShuo Wang <wangshuo47@huawei.com>2020-11-03 14:42:25 +0800
committerShuo Wang <wangshuo47@huawei.com>2020-11-03 14:42:25 +0800
commit74dc7ff245c8ef62744b28d8acbd91a7ef5e0c59 (patch)
treefffccd36a2ccbd7317a217fb70dd9c4696c3ba8e
parente6f3141eb626f703796bd537469221c8261489b5 (diff)
downloadlibevdev-74dc7ff245c8ef62744b28d8acbd91a7ef5e0c59.tar.gz
CODING_STYLE.md: fix a typo
Signed-off-by: Shuo Wang <wangshuo47@huawei.com>
-rw-r--r--CODING_STYLE.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CODING_STYLE.md b/CODING_STYLE.md
index e68de18..c7f62db 100644
--- a/CODING_STYLE.md
+++ b/CODING_STYLE.md
@@ -141,7 +141,7 @@ A [good commit message](http://who-t.blogspot.com/2009/12/on-commit-messages.htm
answer three questions:
- Why is it necessary? It may fix a bug, it may add a feature, it may
- improve performance, reliabilty, stability, or just be a change for the
+ improve performance, reliability, stability, or just be a change for the
sake of correctness.
- How does it address the issue? For short obvious patches this part can be
omitted, but it should be a high level description of what the approach