Merge pull request #862 from w3c/wcag2-x-backlog

Use ' WCAG 2.x Backlog TF' consistently

pages/about/groups/agwg/task-forces.md

@@ -34,7 +34,7 @@ The [Cognitive and Learning Disabilities Accessibility Task Force](/about/groups
 
 ## WCAG 2.x Backlog Task Force
 
-The objective of the [WCAG 2 Task Force](/about/groups/task-forces/wcag2x-backlog/) is to maintain up-to-date versions of the normative and informative materials associated with versions 2.0, 2.1, and 2.2 of the Web Content Accessibility Guidelines, and to document considerations for WCAG 3.0 which cannot be readily addressed within the existing normative language of the 2.x specification.
+The objective of the [WCAG 2.x Backlog Task Force](/about/groups/task-forces/wcag2x-backlog/) is to maintain up-to-date versions of the normative and informative materials associated with versions 2.0, 2.1, and 2.2 of the Web Content Accessibility Guidelines, and to document considerations for WCAG 3.0 which cannot be readily addressed within the existing normative language of the 2.x specification.
 
 ## Low Vision Accessibility Task Force
 

pages/about/groups/task-forces.md

@@ -57,7 +57,7 @@ Task Forces operate under specific Working Groups.
 
 **[WCAG 2.x Backlog Task Force](/about/groups/task-forces/wcag2x-backlog/)** under the [AG Working Group](/about/groups/agwg/)
 
-: The WCAG 2 Task Force maintains up-to-date versions of the normative and informative materials associated with versions 2.0, 2.1, and 2.2 of the Web Content Accessibility Guidelines, and documents considerations for WCAG 3.0 which cannot be readily addressed within the existing normative language of the 2.x specification.
+: The WCAG 2.x Backlog Task Force maintains up-to-date versions of the normative and informative materials associated with versions 2.0, 2.1, and 2.2 of the Web Content Accessibility Guidelines, and documents considerations for WCAG 3.0 which cannot be readily addressed within the existing normative language of the 2.x specification.
 
 
 **[ARIA Authoring Practices Task Force](/about/groups/task-forces/practices/)** under the [ARIA Working Group](/about/groups/ariawg/)

pages/about/groups/task-forces/wcag2x-backlog.md

@@ -37,26 +37,26 @@ Some information on this page is also shown on, and may be more current in, the
 No announcements at the moment.
 
 ## Approach
-The WCAG2 TF is a Task Force of the AG WG, which has oversight over the Task Force to ensure accurate interpretation and representation of WCAG 2.x. The AG WG decision process applies within the group. We have an AG WG co-chair liaison to ensure draft content is taken to the AG WG for review as it progresses.
+The WCAG 2.x Backlog TF is a Task Force of the AG WG, which has oversight over the Task Force to ensure accurate interpretation and representation of WCAG 2.x. The AG WG decision process applies within the group. We have an AG WG co-chair liaison to ensure draft content is taken to the AG WG for review as it progresses.
 
-The WCAG 2 TF has developed a [workflow process](https://github.com/w3c/wcag/wiki/WCAG-2-Task-Force-process) for both creating and vetting pull requests and creating responses to issues. The process also includes a two-week review of all changes by the AG WG.
+The WCAG 2.x Backlog TF has developed a [workflow process](https://github.com/w3c/wcag/wiki/WCAG-2-Task-Force-process) for both creating and vetting pull requests and creating responses to issues. The process also includes a two-week review of all changes by the AG WG.
 
 ## Communication
-The communications of the WCAG 2 Task Force are publicly visible. Communication mechanisms include:
+The communications of the WCAG 2.x Backlog Task Force are publicly visible. Communication mechanisms include:
 
 * [Publicly archived mailing list](https://lists.w3.org/Archives/Public/public-wcag2-issues/);
 * Public [GitHub](https://github.com/w3c/wcag/) and [Wiki](https://github.com/w3c/wcag/wiki) spaces;
 * Public minutes (on the wiki and email list);
 * Regular updates to the AGWG via the [AGWG email list](https://lists.w3.org/Archives/Public/w3c-wai-gl/);
 
 ## Participation
-To join this WCAG 2 Task Force, individuals must be participants of AG WG. Participants are expected to actively contribute to the work of the task force, including:
+To join this WCAG 2.x Backlog Task Force, individuals must be participants of AG WG. Participants are expected to actively contribute to the work of the task force, including:
 
 * Minimum 4 hours per week of task force work (this time also counts towards the individual's participation requirement in the AG WG);
 * Remain current on the task force mailing list and respond in a timely manner to postings;
 * Participate regularly in task force meetings.
 
-If you are interested in becoming a participant of the WCAG 2 Task Force or have any questions regarding its work, contact the task force facilitators.
+If you are interested in becoming a participant of the WCAG 2.x Backlog Task Force or have any questions regarding its work, contact the task force facilitators.
 
 ## Facilitation
 The AG Working Group chair liaison oversees attention to W3C Process with respect to the chartered requirements of the Working Group. The Facilitators set agenda, lead meetings, determine consensus, and are the primary reporters of progress to the Working Group.