diff --git a/common-flow.md b/common-flow.md
index 6021542..069bba8 100644
--- a/common-flow.md
+++ b/common-flow.md
@@ -82,10 +82,10 @@ interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119).
     9. If there is a truly valid technical reason to not use rebase when
        updating change branches, then you can update change branches via merge
        instead of rebase. The decision to use merge MUST only be taken after all
-       possible options to use rebase have been tried and failed. For example,
-       people not understanding how to use rebase is NOT a valid reason to use
-       merge. If you do decide to use merge instead of rebase, you MUST NOT use
-       a mixture of both methods, pick one and stick to it.
+       possible options to use rebase have been tried and failed. People not
+       understanding how to use rebase is NOT a valid reason to use merge. If
+       you do decide to use merge instead of rebase, you MUST NOT use a mixture
+       of both methods, pick one and stick to it.
 4. Pull Requests
     1. To merge a change branch into its merge target, you MUST open a "pull
        request" (or equivalent).