From 8d0bb7d22d18fe1ea7c1d2bf6418323fd8a29171 Mon Sep 17 00:00:00 2001 From: Ben Holden-Crowther Date: Fri, 15 Dec 2017 15:01:04 +0000 Subject: [PATCH] Capitalization and full stops (#605) --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 5b22fbc..129de09 100644 --- a/README.md +++ b/README.md @@ -236,9 +236,9 @@ For example: When you find a closed bug, it is very useful to know which release fixed it. So that you can easily find the issue by \# in `CHANGELOG.md`. -- it's not quite as easy to find this in handwritten releases notes -- a generated file saves you the trouble of remembering everything; - sometimes people forget to add things to a handwritten file +- It's not quite as easy to find this in handwritten releases notes. +- A generated file saves you the trouble of remembering everything; + sometimes people forget to add things to a handwritten file. Ultimately, I think GitHub Releases are ideal for end-users. Meanwhile, `CHANGELOG.md` lives right in the repository, with its detailed list of changes, which is handy for developers.