Merge branch 'master' of https://github.com/kubernetes/website into release-1.9

* 'master' of https://github.com/kubernetes/website: (549 commits)
  Update service.md (#7810)
  Prune inactive maintainers (#7830)
  add Amadeus to index page and add feature image (#7827)
  Update conventions.md (#7668)
  Adding Tenxcloud as KCSP and Hedvig typo (#7826)
  Update outdated documentation about secret key validation. (#7675)
  Update imperative-command.md (#7699)
  Update manage-deployment.md (#7774)
  Add the OCI runtime description. (#7769)
  fix flag (#7814)
  fix flag (#7813)
  Add files via upload (#7816)
  Remove CoreOS guide that use Kubernetes v0.15.0 (#7821)
  "Nagions" should be "Nagios“ (#7762)
  Update docker-cli-to-kubectl.md (#7748)
  adjust a note format (#7812)
  add a note when mount a configmap to pod (#7745)
  Make using sysctls a task instead of a concept (#6808)
  Partners page updates (#7802)
  Fix a missing word in endpoint reconciler section (#7804)
  ...

docs/tasks/administer-cluster/reconfigure-kubelet.md

@@ -1,5 +1,5 @@
 ---
-approvers:
+reviewers:
 - mtaufen
 - dawnchen
 title: Reconfigure a Node's Kubelet in a Live Cluster
@@ -290,7 +290,7 @@ configSource:
 ### Observe that the Kubelet is using the new configuration
 
 Once more, retrieve the Node with `kubectl get node ${NODE_NAME} -o yaml`, and
-look for the `ConfigOK` condition in `status.conditions`. You should the message
+look for the `ConfigOK` condition in `status.conditions`. You should see the message
 `Using current (UID: NEW_CONFIG_MAP_UID)` when the Kubelet starts using the
 new configuration.
 
@@ -333,7 +333,7 @@ condition's message reverts to either `using current (default)` or
 
 ### Deauthorize your Node fom reading the old ConfigMap
 
-Once you know your Node is using the default configuraiton again, it is a good
+Once you know your Node is using the default configuration again, it is a good
 idea to deauthorize the node from reading the old ConfigMap. Run the following
 commands to remove the RoleBinding and Role: