Change 'minion' to 'node' in docs

docs/getting-started-guides/coreos/azure/README.md

@@ -56,7 +56,7 @@ Now, all you need to do is:
 ./create-kubernetes-cluster.js
 ```
 
-This script will provision a cluster suitable for production use, where there is a ring of 3 dedicated etcd nodes, 1 kubernetes master and 2 kubernetes nodes. The `kube-00` VM will be the master, your work loads are only to be deployed on the nodes, `kube-01` and `kube-02`. Initially, all VMs are single-core, to ensure a user of the free tier can reproduce it without paying extra. I will show how to add more bigger VMs later.
+This script will provision a cluster suitable for production use, where there is a ring of 3 dedicated etcd nodes: 1 kubernetes master and 2 kubernetes nodes. The `kube-00` VM will be the master, your work loads are only to be deployed on the nodes, `kube-01` and `kube-02`. Initially, all VMs are single-core, to ensure a user of the free tier can reproduce it without paying extra. I will show how to add more bigger VMs later.
 
 ![VMs in Azure](initial_cluster.png)
 

docs/getting-started-guides/coreos/azure/cloud_config_templates/kubernetes-cluster-main-nodes-template.yml

@@ -17,7 +17,7 @@ write_files:
     owner: root
     content: |
       #!/bin/sh -xe
-      minion_id="${1}"
+      node_id="${1}"
       master_url="${2}"
       env_label="${3}"
       until healthcheck=$(curl --fail --silent "${master_url}/healthz")
@@ -31,7 +31,7 @@ write_files:
         "metadata": {
           "name": "%s",
           "labels": { "environment": "%s" }
-        }' "${minion_id}" "${env_label}" \
+        }' "${node_id}" "${env_label}" \
         | /opt/bin/kubectl create -s "${master_url}" -f -
 
   - path: /etc/kubernetes/manifests/fluentd.manifest