From a6a1ee1d85a84d7eaed1f08c780f8ba81878c1af Mon Sep 17 00:00:00 2001 From: Steve Schnepp Date: Tue, 20 Jan 2015 22:06:40 +0100 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 26343f3f..46578d99 100644 --- a/README.md +++ b/README.md @@ -42,7 +42,7 @@ as merging one, if not easier. A good rationale is that each commit shall have a one-liner commit comment as its first line. Ideally that first line has a prefix that shows the part the commit is about. It makes it very -easy to see grouped changes, and it enable avoiding to look at the --stat. To know the prefix you should +easy to see grouped changes, and it enable avoiding to look at the `--stat`. To know the prefix you should use, you can have a look at already existing commits. Next lines are optional and should only explain the _why_ it is done this particular way.