Edits from Xueyuan

Author: ianbjacobs

process/adv-notice.md

@@ -3,7 +3,7 @@ title: Announcing the start of Charter Refinement
 toc: yes
 ---
 
-The W3C Process defines a [charter refinement phase](https://www.w3.org/policies/process/drafts/#charter-initiation) to help ensure that draft charters are mission-aligned, reflect community input and consensus, and have been well-socialized and widely reviewed *before* formal review by the Advisory Committee. 
+The W3C Process defines a [charter refinement phase](https://www.w3.org/policies/process/drafts/#charter-initiation) to help ensure that charter drafts are mission-aligned, reflect community input and consensus, and have been well-socialized and widely reviewed *before* Advisory Committee review.
 
 This document describes how the W3C Communications Team announces the
 start of charter refinement with a *charter review notice*. For
@@ -24,7 +24,7 @@ Per [section 4.1 of the Process Document](https://www.w3.org/policies/process/dr
 
 In addition, the Strategy Team *may* include its own perspectives about the charter in the review notice.
 
-Please use the [advance notice template](https://www.w3.org/new-doc-from-template?location=%2FTeam%2F&template=%2Fafs%2Fw3.org%2Fpub%2FWWW%2FTeam%2FTemplates%2Fcharter-review-notice.html&submit=Continue...) to create an initial draft.
+Please use the [charter review notice template](https://www.w3.org/new-doc-from-template?location=%2FTeam%2F&template=%2Fafs%2Fw3.org%2Fpub%2FWWW%2FTeam%2FTemplates%2Fcharter-review-notice.html&submit=Continue...) to create an initial draft.
 
 # Sending the charter review notice
 
@@ -44,4 +44,4 @@ to:
 
 [Section 4.2 of the Process Document](https://www.w3.org/policies/process/drafts/#charter-development) describes activities during the refinement phase, and in particular the role of the Charter Facilitator to seek consensus and how and when any Formal Objections are handled.
 
-**Note**: Advance notice is not an indication that work *will* necessarily progress to formal Advisory Committee review.
+**Note**: Advance notice is not an indication that work *will* necessarily progress to Advisory Committee review.

process/charter.md

@@ -17,7 +17,7 @@ W3C creates charters for Working and Interest Groups based on W3C community inte
 
 In this document we describe the operational aspects of these phases.
 
-**Note**: Organizing discussions and reviews, building consensus, and handling of formal objections all require time. People working on charters should expect the entire process to take multiple months.
+**Note**: Organizing discussions and reviews, building consensus, and handling of Formal Objections all require time. People working on charters should expect the entire process to take multiple months.
 
 ## 2. Team Decisions
 
@@ -70,7 +70,7 @@ Verify transition readiness
 : For a Working Group charter, review: [W3C Recommendation Track Readiness Best Practices](../standards-track/), [Tips for Getting to Recommendation Faster](https://www.w3.org/2002/05/rec-tips), and [How to transition work from a Community Group to a Working Group](cg-transition.md).
 
 Draft a charter
-: Use the [charter template](https://w3c.github.io/charter-drafts/charter-template.html) to create a public draft charter, [ideally on GitHub](https://w3c.github.io/charter-drafts/). This is where substantive discussion of the charter should take place, including issues and pull requests.
+: Use the [charter template](https://w3c.github.io/charter-drafts/charter-template.html) to create a public charter draft, [ideally on GitHub](https://w3c.github.io/charter-drafts/). This is where substantive discussion of the charter should take place, including issues and pull requests.
 
 Inform the Strategy Team
 : When ready (e.g., after sufficient discussion among stakeholders has taken place), inform the Strategy Team by [creating a new charter issue](https://github.com/w3c/strategy/issues/new?assignees=&labels=Evaluation%3A%20untriaged&template=04-Chartering.md&title=) in their [pipeline](#pipeline).  The Strategy Team uses this issue to provide updates on the charter's progress through the process. Discussions of the charter's content should continue to take place in the charter's own repo.