From 4f6b8f8e150f40a766c3918c3622b1a91cc01218 Mon Sep 17 00:00:00 2001 From: Jim Myhrberg Date: Fri, 29 Dec 2017 01:32:02 +0000 Subject: [PATCH] Improve grammar and clarify reason for using PR's for help/feedback --- common-flow.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/common-flow.md b/common-flow.md index aef2b65..c36f657 100644 --- a/common-flow.md +++ b/common-flow.md @@ -102,8 +102,9 @@ interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119). happy with the change. This is especially important if the merge target is the master branch. 5. To get feedback, help, or generally just discuss a change branch with - others, the RECOMMENDED way to do so is by creating a pull request and - discuss the changes with others there. + others, it is RECOMMENDED you create a pull request and discuss the + changes with others there. This leaves a clear and visible history of + how, when, and why the code looks and behaves the way it does. 5. Versioning 1. A "version string" is a typically mostly numeric string that identifies a specific version of a project. The version string itself MUST NOT have a