Apply suggestions from code review (maintain line length).

Co-authored-by: Ted Thibodeau Jr <[email protected]>

CGCharter-1727386911.html

@@ -227,9 +227,11 @@ <h2 id="decision">
       Decision Process
     </h2>
     <p>
-      This group will seek to make decisions where there is consensus. The Group makes decisions in the following ways: either Committers assess
-      consensus, or the Chair assesses consensus, or where consensus isn't
-      clear there is a <a href="#calls-for-consensus">Call for Consensus</a>  [CfC] (see below) to allow multi-day
+      This group will seek to make decisions where there is consensus. The
+      Group makes decisions in the following ways: either Committers assess
+      consensus; the Chair assesses consensus; or, where consensus isn't
+      clear, there is a <a href="#calls-for-consensus">Call for Consensus</a>
+      [CfC] (see below) to allow multi-day
       online feedback for a proposed course of action.
       After discussion and due consideration of different opinions, a decision
       should be publicly recorded (where GitHub is used as the resolution
@@ -257,7 +259,10 @@ <h3 id="calls-for-consensus">
     </h3>
     <p>
       A call for consensus (CfC) will be issued for all resolutions via
-      email to [email protected]. The presence of formal resolutions will be indicated by a "CfC" prefix in the subject line of an email on the list. Additional outreach to community venues for more affirmative consent is strongly encouraged.
+      email to [email protected]. The presence of formal resolutions will be
+      indicated by a "CfC" prefix in the subject line of an email on the list.
+      Additional outreach to community venues for more affirmative consent is
+      strongly encouraged.
     </p>
     <p>
       There will be