updated for 2.1

_planning-and-managing/plan.md

@@ -5,7 +5,7 @@ title_icon: /planning-and-managing/img/icons.svg#plan
 github:
   repository: w3c/wai-planning-and-managing
 footer: >
-  <p><strong>Date:</strong> Updated 31 March 2016. First published October 2002.</p>
+  <p><strong>Date:</strong> Minor updates 24 May 2018. Updated 31 March 2016. First published October 2002.</p>
   <p><strong>Editors:</strong> <a href="https://www.w3.org/People/kevin">Kevin White</a>, <a href="https://www.w3.org/People/shadi">Shadi Abou-Zahra</a>, and <a href="https://www.w3.org/People/Shawn">Shawn Lawton Henry</a>. <a href="https://www.w3.org/WAI/beta/planning-and-managing/acknowledgements/">Acknowledgements</a> includes information on previous versions and editors.</p>
   <p>Developed by the Education and Outreach Working Group (<a href="http://www.w3.org/WAI/EO/">EOWG</a>). Updated with support from the <a href="https://www.w3.org/WAI/DEV/">WAI-DEV Project</a> and the <a href="https://www.w3.org/WAI/ACT/">WAI-ACT Project</a>, co-funded by the European Commission <abbr title="Information Society Technologies">IST</abbr> Programme.</p>
 ---
@@ -29,7 +29,7 @@ A web accessibility policy captures your goals and targets. Policies
 vary across organizations but at a minimum establishes what web
 accessibility standard you aim to conform to and by when. For example,
 your policy might only state that your website will meet all criteria
-specified in WCAG 2.0 Level AA within one year. A policy may cover other
+specified in WCAG 2.1 Level AA within one year. A policy may cover other
 topics such as roles and responsibilities, content preparation
 processes, quality assurance, infrastructure, and reporting.
 
@@ -217,7 +217,7 @@ skills and experience needed to undertake a thorough review.
 
 ### For more information
 
--   [WCAG-EM Overview]({{ "/test-evaluate/conformance/" | relative_url }}) – Introduces a methodology for determining how well a website conforms to WCAG 2.0.
+-   [WCAG-EM Overview]({{ "/test-evaluate/conformance/" | relative_url }}) – Introduces a methodology for determining how well a website conforms to WCAG 2.
 -   [Assess the Situation](/WAI/impl/improving#assess) – Describes how
     you might approach evaluating your website.
 -   [Involving Users in Web Projects for Better, Easier Accessibility](/WAI/users/involving) – Describes the benefits of involving users in projects and how to go about it.
@@ -239,7 +239,7 @@ has occurred.
 
 Some example criteria include:
 
--   Number of WCAG 2.0 Success Criteria passed, and their level.
+-   Number of WCAG 2 Success Criteria passed, and their level.
 -   Number of complaints received related to accessibility.
 -   Calls handled from people who were unable to process their
     application online.