fix typos

docs/user-guide/federation/configmap.md

@@ -43,11 +43,11 @@ kubectl --context=federation-cluster create -f myconfigmap.yaml
 ```
 
 The `--context=federation-cluster` flag tells kubectl to submit the
-request to the Federation apiserver instead of sending it to a kubernetes
+request to the Federation apiserver instead of sending it to a Kubernetes
 cluster.
 
 Once a Federated ConfigMap is created, the federation control plane will create
-a matching ConfigMap in all underlying kubernetes clusters.
+a matching ConfigMap in all underlying Kubernetes clusters.
 You can verify this by checking each of the underlying clusters, for example:
 
 ``` shell

docs/user-guide/federation/daemonsets.md

@@ -44,11 +44,11 @@ kubectl --context=federation-cluster create -f mydaemonset.yaml
 ```
 
 The `--context=federation-cluster` flag tells kubectl to submit the
-request to the Federation apiserver instead of sending it to a kubernetes
+request to the Federation apiserver instead of sending it to a Kubernetes
 cluster.
 
 Once a Federated Daemonset is created, the federation control plane will create
-a matching DaemonSet in all underlying kubernetes clusters.
+a matching DaemonSet in all underlying Kubernetes clusters.
 You can verify this by checking each of the underlying clusters, for example:
 
 ``` shell

docs/user-guide/federation/deployment.md

@@ -47,11 +47,11 @@ kubectl --context=federation-cluster create -f mydeployment.yaml
 ```
 
 The '--context=federation-cluster' flag tells kubectl to submit the
-request to the Federation apiserver instead of sending it to a kubernetes
+request to the Federation apiserver instead of sending it to a Kubernetes
 cluster.
 
 Once a Federated Deployment is created, the federation control plane will create
-a Deployment in all underlying kubernetes clusters.
+a Deployment in all underlying Kubernetes clusters.
 You can verify this by checking each of the underlying clusters, for example:
 
 ``` shell

docs/user-guide/federation/events.md

@@ -27,7 +27,7 @@ general.
 Events in federation control plane (referred to as "federation events" in
 this guide) are very similar to the traditional Kubernetes
 Events providing the same functionality.
-Federation Events are stored only in federation control plane and are not passed on to the underlying kubernetes clusters.
+Federation Events are stored only in federation control plane and are not passed on to the underlying Kubernetes clusters.
 
 Federation controllers create events as they process API resources to surface to the
 user, the state that they are in.

docs/user-guide/federation/federated-ingress.md

@@ -277,7 +277,7 @@ where:
 
 1. `firewall-rule-name` can be any name.
 2. `[<service-nodeports>]` is the comma separated list of node ports corresponding to the services that back the Federated Ingress.
-3. [<target-tags>] is the comma separated list of the target tags assigned to the nodes in a kubernetes cluster.
+3. [<target-tags>] is the comma separated list of the target tags assigned to the nodes in a Kubernetes cluster.
 4. <network-name> is the name of the network where the firewall rule must be installed.
 
 Example:

docs/user-guide/federation/index.md

@@ -2,7 +2,7 @@
 title: Federation User Guide
 ---
 
-This guide explains how we can manage multiple kubernetes clusters using
+This guide explains how we can manage multiple Kubernetes clusters using
 federation.
 [Federation proposal](https://github.com/kubernetes/kubernetes/blob/{{page.githubbranch}}/docs/proposals/federation.md)
 details the use cases motivating cluster federation.

docs/user-guide/federation/namespaces.md

@@ -43,11 +43,11 @@ kubectl --context=federation-cluster create -f myns.yaml
 ```
 
 The '--context=federation-cluster' flag tells kubectl to submit the
-request to the Federation apiserver instead of sending it to a kubernetes
+request to the Federation apiserver instead of sending it to a Kubernetes
 cluster.
 
 Once a federated namespace is created, the federation control plane will create
-a matching namespace in all underlying kubernetes clusters.
+a matching namespace in all underlying Kubernetes clusters.
 You can verify this by checking each of the underlying clusters, for example:
 
 ``` shell
@@ -64,7 +64,7 @@ the Federated Namespace that you created above.
 
 You can update a federated namespace as you would update a Kubernetes
 namespace, just send the request to federation apiserver instead of sending it
-to a specific kubernetes cluster.
+to a specific Kubernetes cluster.
 Federation control plan will ensure that whenever the federated namespace is
 updated, it updates the corresponding namespaces in all underlying clusters to
 match it.
@@ -73,7 +73,7 @@ match it.
 
 You can delete a federated namespace as you would delete a Kubernetes
 namespace, just send the request to federation apiserver instead of sending it
-to a specific kubernetes cluster.
+to a specific Kubernetes cluster.
 
 For example, you can do that using kubectl by running:
 

docs/user-guide/federation/replicasets.md

@@ -43,11 +43,11 @@ kubectl --context=federation-cluster create -f myrs.yaml
 ```
 
 The '--context=federation-cluster' flag tells kubectl to submit the
-request to the Federation apiserver instead of sending it to a kubernetes
+request to the Federation apiserver instead of sending it to a Kubernetes
 cluster.
 
 Once a federated replica set is created, the federation control plane will create
-a replica set in all underlying kubernetes clusters.
+a replica set in all underlying Kubernetes clusters.
 You can verify this by checking each of the underlying clusters, for example:
 
 ``` shell

docs/user-guide/federation/secrets.md

@@ -43,11 +43,11 @@ kubectl --context=federation-cluster create -f mysecret.yaml
 ```
 
 The '--context=federation-cluster' flag tells kubectl to submit the
-request to the Federation apiserver instead of sending it to a kubernetes
+request to the Federation apiserver instead of sending it to a Kubernetes
 cluster.
 
 Once a federated secret is created, the federation control plane will create
-a matching secret in all underlying kubernetes clusters.
+a matching secret in all underlying Kubernetes clusters.
 You can verify this by checking each of the underlying clusters, for example:
 
 ``` shell