diff --git a/README.md b/README.md
index 8f9e8b608..6adcd7a10 100644
--- a/README.md
+++ b/README.md
@@ -334,10 +334,10 @@ sriov-vlanid-l2enable-conf   Network.v1.kubernetes.com
 sriov-conf                   Network.v1.kubernetes.com
 ```
 ### Configuring Multus to use the kubeconfig
-1.	Create Multus CNI configuration file /etc/cni/net.d/multus-cni.conf with below content in minions. Use only the absolute path to point to the kubeconfig file (it may change depending upon your cluster env) and make sure all CNI binary files are in `\opt\cni\bin` dir
+1.	Create Multus CNI configuration file /etc/cni/net.d/multus-cni.conf with below content on the nodes. Use only the absolute path to point to the kubeconfig file (it may change depending upon your cluster env) and make sure all CNI binary files are in `\opt\cni\bin` dir
 ```
 {
-    "name": "minion-cni-network",
+    "name": "node-cni-network",
     "type": "multus",
     "kubeconfig": "/etc/kubernetes/node-kubeconfig.yaml"
 }
@@ -350,7 +350,7 @@ sriov-conf                   Network.v1.kubernetes.com
 1.	Many user want default networking feature along with Network object. Refer [#14](https://github.com/Intel-Corp/multus-cni/issues/14) & [#17](https://github.com/Intel-Corp/multus-cni/issues/17) issues for more information. In this following config, Weave act as the default network in the absence of network field in the pod metadata annotation.
 ```
 {
-    "name": "minion-cni-network",
+    "name": "node-cni-network",
     "type": "multus",
     "kubeconfig": "/etc/kubernetes/node-kubeconfig.yaml",
     "delegates": [{