Merge pull request #1283 from YuPengZTE/devFirst

Capitalizes the first letter

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

@@ -40,9 +40,9 @@ API for traditional Kubernetes Services.
 
 Once created, the Federated Service automatically:
 
-1. creates matching Kubernetes Services in every cluster underlying your Cluster Federation,
-2. monitors the health of those service "shards" (and the clusters in which they reside), and
-3. manages a set of DNS records in a public DNS provider (like Google Cloud DNS, or AWS Route 53), thus ensuring that clients
+1. Creates matching Kubernetes Services in every cluster underlying your Cluster Federation,
+2. Monitors the health of those service "shards" (and the clusters in which they reside), and
+3. Manages a set of DNS records in a public DNS provider (like Google Cloud DNS, or AWS Route 53), thus ensuring that clients
 of your federated service can seamlessly locate an appropriate healthy service endpoint at all times, even in the event of cluster,
 availability zone or regional outages.
 

docs/user-guide/images.md

@@ -118,12 +118,12 @@ in the `$HOME` of user `root` on a kubelet, then docker will use it.
 Here are the recommended steps to configuring your nodes to use a private registry.  In this
 example, run these on your desktop/laptop:
 
-   1. run `docker login [server]` for each set of credentials you want to use.  This updates `$HOME/.docker/config.json`.
-   1. view `$HOME/.docker/config.json` in an editor to ensure it contains just the credentials you want to use.
-   1. get a list of your nodes, for example:
+   1. Run `docker login [server]` for each set of credentials you want to use.  This updates `$HOME/.docker/config.json`.
+   1. View `$HOME/.docker/config.json` in an editor to ensure it contains just the credentials you want to use.
+   1. Get a list of your nodes, for example:
       - if you want the names: `nodes=$(kubectl get nodes -o jsonpath='{range.items[*].metadata}{.name} {end}')`
       - if you want to get the IPs: `nodes=$(kubectl get nodes -o jsonpath='{range .items[*].status.addresses[?(@.type=="ExternalIP")]}{.address} {end}')`
-   1. copy your local `.docker/config.json` to the home directory of root on each node.
+   1. Copy your local `.docker/config.json` to the home directory of root on each node.
       - for example: `for n in $nodes; do scp ~/.docker/config.json root@$n:/root/.docker/config.json; done`
 
 Verify by creating a pod that uses a private image, e.g.:

docs/user-guide/jobs/expansions/index.md

@@ -32,7 +32,7 @@ We also put the same label on the pod template so that we can check on all Pods
 with a single command.
 After the job is created, the system will add more labels that distinguish one Job's pods
 from another Job's pods.
-Note that the label key `jobgroup` is not special to Kubernetes. you can pick your own label scheme.
+Note that the label key `jobgroup` is not special to Kubernetes. You can pick your own label scheme.
 
 Next, expand the template into multiple files, one for each item to be processed.