From d4f4f88009159bc449e10d48556a991ad9ba1a29 Mon Sep 17 00:00:00 2001 From: Jim Myhrberg Date: Tue, 30 Jan 2018 13:02:04 +0000 Subject: [PATCH] Improve wording of Summary section --- common-flow.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/common-flow.md b/common-flow.md index 41bcca7..e4b4b5b 100644 --- a/common-flow.md +++ b/common-flow.md @@ -41,12 +41,12 @@ Summary be broken. - Changes (features, bugfixes, etc.) are done on "change branches" created from the master branch. -- [Rebase early and often.](https://i.imgur.com/1RS8x2d.png) +- Rebase change branches [early and often](https://i.imgur.com/1RS8x2d.png). - When a change branch is stable and ready, it is merged back in to master. - A release is just a git tag who's name is the exact release version string (e.g. "2.11.4"). - Release branches can be used to avoid a change freezes on master. They are not - required, instead they are available if you do need them. + required, instead they are available if you need them. Git Common-Flow Specification (Common-Flow) -------------------------------------------