fix kubemark, juju, and libvirt-coreos README.md (from minion to node)

cluster/juju/bundles/README.md

@@ -51,7 +51,7 @@ The command above does few things for you:
   deployment environment (machine 0).
 - Deploys the Juju GUI to your environment onto the bootstrap node.
 - Provisions 4 machines, and deploys the Kubernetes services on top of
-  them (Kubernetes-master, two Kubernetes minions using flannel, and etcd).
+  them (Kubernetes-master, two Kubernetes nodes using flannel, and etcd).
 - Orchestrates the relations among the services, and exits.
 
 Now you should have a running Kubernetes. Run `juju status
@@ -113,9 +113,9 @@ capabilities to the charms.
 The master controls the Kubernetes cluster.  It manages for the worker
 nodes and provides the primary interface for control by the user.
 
-### Kubernetes minion
+### Kubernetes node
 
-The minions are the servers that perform the work.  Minions must
+The nodes are the servers that perform the work.  Nodes must
 communicate with the master and run the workloads that are assigned to
 them.
 

cluster/libvirt-coreos/README.md

@@ -1,7 +1,7 @@
 # Kubernetes CoreOS cluster
 
 With this tutorial one creates a Kubernetes CoreOS cluster containing of one
-master and three minions (workers) running on `192.168.10.1`-`192.168.10.4`.
+master and three nodes (workers) running on `192.168.10.1`-`192.168.10.4`.
 
 For working correctly you need to create the directory addressed as `POOL_PATH` in
 `util.sh`:

test/kubemark/pre-existing/README.md

@@ -4,7 +4,7 @@
 - A set of Kubernetes control plane components running in a VM
 
 **Kubernetes Cluster**
-- A real Kubernetes Cluster that has master and minions. The hollow-node pods
+- A real Kubernetes Cluster that has master and nodes. The hollow-node pods
   are run in this cluster, but appear as nodes to the Kubemark Master
 
 ## Introduction