More typos in the Charter page (#365)

Author: tidoust

process/charter.md

@@ -39,7 +39,7 @@ The [Technical Strategy Team](https://www.w3.org/staff/strat/) and [Project &amp
 ### 2.2 Chartering Facilitator
 {:#chartering-facilitator}
 
-The [Technical Strategy Team Lead](https://www.w3.org/staff/strat/) or the [Project & Process Team Lead](https://www.w3.org/staff/project/) choose (and may replace) a *Chartering Facilitator* to shepherd a given charter through the process. The Chartering Facilitator is typically from the Staff but is not required to be from the Staff. In the case of rechartering it is common to name the group's [Staff Contact](../teamcontact/role.md) as the Chartering Facilitator.
+The [Technical Strategy Team Lead](https://www.w3.org/staff/strat/) or the [Project & Process Team Lead](https://www.w3.org/staff/project/) chooses (and may replace) a *Chartering Facilitator* to shepherd a given charter through the process. The Chartering Facilitator is typically from the Staff but is not required to be from the Staff. In the case of rechartering it is common to name the group's [Staff Contact](../teamcontact/role.md) as the Chartering Facilitator.
 
 **Note:** If the Team Leads cannot identify a Chartering Facilitator, there may be delays in advancing the charter through the process.
 
@@ -98,10 +98,10 @@ Select a Chartering Facilitator
 : For the rechartering of existing groups, the Team Contact is selected by default as Chartering Facilitator and should assign the github issue to themselves. Otherwise, the [Technical Strategy Team Lead](https://www.w3.org/staff/strat/) or [Project & Process Team Lead](https://www.w3.org/staff/project/) select a [Chartering Facilitator](#chartering-facilitator) and records that appointment in the [pipeline](#pipeline) by assigning github issues.
 
 Request announcement of initiation of charter refinement
-: The [Chartering Facilitator](#chartering-facilitator) then sends a request to the W3C Communications Team to [announce the initiation of charter refinement](adv-notice.md), copying the Technical Strategy Team Lead](https://www.w3.org/staff/strat/) and the [Project & Process Team Lead](https://www.w3.org/staff/project/); that document lists requirements for the announcement. In practice, if the announcement would precede the call for AC review by only a short delay, we skip the refinement phase.
+: The [Chartering Facilitator](#chartering-facilitator) then sends a request to the W3C Communications Team to [announce the initiation of charter refinement](adv-notice.md), copying the [Technical Strategy Team Lead](https://www.w3.org/staff/strat/) and the [Project & Process Team Lead](https://www.w3.org/staff/project/); that document lists requirements for the announcement. In practice, if the announcement would precede the call for AC review by only a short delay, we skip the refinement phase.
 
 Record start of refinement
-: Once refinement has been announced, the Technical Strategy Team Lead](https://www.w3.org/staff/strat/) or [Project & Process Team Lead](https://www.w3.org/staff/project/) records the initiation of charter refinement in the [pipeline](#pipeline) issue.
+: Once refinement has been announced, the [Technical Strategy Team Lead](https://www.w3.org/staff/strat/) or [Project & Process Team Lead](https://www.w3.org/staff/project/) records the initiation of charter refinement in the [pipeline](#pipeline) issue.
 
 Any Formal Objection to a Team Decision to initiate charter refinement is not considered registered until the close of any Advisory Committee Review of that charter, and is registered against that W3C Decision.