Merge pull request #2764 from SataQiu/fix-20181008

fix typo

communication/meeting-notes-archive/q1-2_2018_community_meeting_minutes.md

@@ -1737,7 +1737,7 @@
         *   Ask current contributors anything on slack #meet-our-contributors - testing infra, how to make first time contribution, how did they get involved in k8s
     *   Shoutouts!
         *   None on slack this week, thank someone in #shoutouts!
-        *   Top 5 in the the Kubernetes StackOverflow tag for the week: Radek "Goblin" Pieczonka, aerokite, Vikram Hosakote, Jonah Benton, and fiunchinho
+        *   Top 5 in the Kubernetes StackOverflow tag for the week: Radek "Goblin" Pieczonka, aerokite, Vikram Hosakote, Jonah Benton, and fiunchinho
 
 
 ## February 22, 2018 - ([recording](https://www.youtube.com/watch?v=7pN0xdiFqPE))

contributors/design-proposals/multicluster/federated-replicasets.md

@@ -286,7 +286,7 @@ enumerated the key idea elements:
    + [E1] Master rejects LRS creation (for known or unknown
       reason). In this case another attempt to create a LRS should be
       attempted in 1m or so. This action can be tied with
-      [[I5]](#heading=h.ififs95k9rng). Until the the LRS is created
+      [[I5]](#heading=h.ififs95k9rng). Until the LRS is created
       the situation is the same as [E5]. If this happens multiple
       times all due replicas should be moved elsewhere and later moved
       back once the LRS is created.

contributors/guide/owners.md

@@ -84,7 +84,7 @@ filters:
 Instead, set a `.*` key inside `filters` (as shown in the previous example).
 
 **WARNING**: The `approve` plugin [does not currently respect `filters`][test-infra-7690].
-Until that is fixed, `filters` should only be used for the the `labels` key (as shown in the above example).
+Until that is fixed, `filters` should only be used for the `labels` key (as shown in the above example).
 
 ### OWNERS_ALIASES
 

events/2017/12-contributor-summit/steering-committee-update.md

@@ -10,7 +10,7 @@ We had a meeting, and the two big items we'd been pushing on hard were:
 * votining in the proposals in the bootstrap committee
 * how we're going to handle incubator and contrib etc.
 
-Incubator/contrib: one of our big concerns are what the the consequences for projects and ecosystems.
+Incubator/contrib: one of our big concerns are what the consequences for projects and ecosystems.
 We're still discussing it, please be patient.  In the process of solving the incubator process, we have to answer
 what is kubernetes, which is probably SIGs, but what's a SIG, and who decides, and ...  we end up having to examine
 everything.  In terms of deciding what is and isn't kubernetes, we want to have that discussion in the open.

events/community-meeting.md

@@ -48,7 +48,7 @@ The first 10 minutes of a meeting is dedicated to demonstrations from the commun
 These demos are noted at the top of the community document. 
 There is a hard stop of the demo at 10 minutes, with up to 5 more minutes for questions.
 Feel free to add your demo request to the bottom of the list, then one of the organizers will get back to you to schedule an exact date. 
-Demo submissions MUST follow the the requirements listed below. 
+Demo submissions MUST follow the requirements listed below. 
 
 ### Requirements
 

sig-architecture/api-review-process.md

@@ -193,7 +193,7 @@ Once the provisional review has been accepted by the approver, it then goes to t
 
 As aspiring reviewers gain proficiency, they may pair with an approver on time-sensitive reviews to better understand the process with less impact on the review duration. 
 
-Aspiring reviewers should reach out the the moderator on slack.  The moderator will add them to the list of aspiring reviewers and assign training reviews as they become available. 
+Aspiring reviewers should reach out the moderator on slack.  The moderator will add them to the list of aspiring reviewers and assign training reviews as they become available. 
 
 ## Aspirations for future iterations of this process