Reduce coupling with the Bylaws

The Process only needs to concern itself with the fact that the bylaws
define that Consortium Members have Consortium Member Representatives,
and that some Members (in the sense of the Process) do not qualify to be
Consortium Members (and thus don't have a C.M.Rep.). It does not need to
concern itself with why the bylaws exclude some organisations from being
Consortium Members, and therefore reducing the interdependency is
desirable: this allows the bylaws to evolve the criteria if needed,
without needing any revision in the Process.

Author: frivoal

index.bs

@@ -767,12 +767,13 @@ Participation in the Advisory Committee</h4>
 	of <a href="https://www.w3.org/Member/ACList">current Advisory Committee representatives</a>. [[CURRENT-AC]])
 
 	As defined in the W3C Bylaws,
-	each “<i>Consortium Member</i>” (that is, each W3C [=Member=] organization that is not a [=Member Association=])
+	each “<i>Consortium Member</i>”
 	has one “<i>Consortium Member Representative</i>” [[!BYLAWS]].
 	For purposes of the W3C Process,
 	this person also serves as the organization's [=Advisory Committee Representative=].
-	When a [=Member Association=] joins W3C,
-	it <em class=rfc2119>must</em> name its [=Advisory Committee representative=].
+	When a [=Member=] does not qualify as a “<i>Consortium Member</i>”,
+	it <em class=rfc2119>must</em> name its [=Advisory Committee representative=]
+	upon joining W3C.
 	The <a href="https://www.w3.org/Member/Intro">New Member Orientation</a> [[INTRO]]
 	explains how to subscribe or unsubscribe to Advisory Committee mailing lists,
 	provides information about <a href="#ACMeetings">Advisory Committee Meetings</a>,