Update use-tags.md

Correct tag of node resource group from nodepool to cluster.

Author: tdihp

articles/aks/use-tags.md

@@ -38,6 +38,7 @@ It's a good idea to understand what happens when you set and update Azure tags w
 When you create or update an AKS cluster with the `--tags` parameter, the following are assigned the Azure tags that you've specified:
 
 * The AKS cluster
+* The node resource group
 * The route table that's associated with the cluster
 * The public IP that's associated with the cluster
 * The network security group that's associated with the cluster
@@ -46,7 +47,7 @@ When you create or update an AKS cluster with the `--tags` parameter, the follow
 To create a cluster and assign Azure tags, run `az aks create` with the `--tags` parameter, as shown in the following command. Running the command creates a *myAKSCluster* in the *myResourceGroup* with the tags *dept=IT* and *costcenter=9999*.
 
 > [!NOTE]
-> To set tags on the initial node pool, the node resource group, the virtual machine scale set, and each virtual machine scale set instance that's associated with the initial node pool, also set the `--nodepool-tags` parameter.
+> To set tags on the initial node pool, the virtual machine scale set, and each virtual machine scale set instance that's associated with the initial node pool, also set the `--nodepool-tags` parameter.
 
 ```azurecli-interactive
 az aks create \
@@ -103,7 +104,6 @@ You can apply an Azure tag to a new or existing node pool in your AKS cluster. T
 When you create or update a node pool with the `--tags` parameter, the tags that you specify are assigned to the following resources:
 
 * The node pool
-* The node resource group
 * The virtual machine scale set and each virtual machine scale set instance that's associated with the node pool
 
 To create a node pool with an Azure tag, run `az aks nodepool add` with the `--tags` parameter. Running the following command creates a *tagnodepool* node pool with the tags *abtest=a* and *costcenter=5555* in the *myAKSCluster*.
@@ -203,4 +203,4 @@ parameters:
 > 
 > Any updates that you make to tags through Kubernetes will retain the value that's set through Kubernetes. For example, if your disk has tags *dept=IT* and *costcenter=5555* set by Kubernetes, and you use the portal to set the tags *team=beta* and *costcenter=3333*, the new list of tags would be *dept=IT*, *team=beta*, and *costcenter=5555*. If you then remove the disk through Kubernetes, the disk would have the tag *team=beta*.
 
-[install-azure-cli]: /cli/azure/install-azure-cli
+[install-azure-cli]: /cli/azure/install-azure-cli