CNV-21804: master changed to control plane

Signed-off-by: Avital Pinnick <[email protected]>

Author: apinnick

modules/virt-troubleshooting-incorrect-policy-config.adoc

@@ -1,6 +1,5 @@
 // Module included in the following assemblies:
 //
-// * virt/node_network/virt-troubleshooting-node-network.adoc
 // * networking/k8s_nmstate/k8s-nmstate-troubleshooting-node-network.adoc
 
 :_content-type: PROCEDURE
@@ -10,7 +9,7 @@
 You can apply changes to the node network configuration across your entire cluster by applying a node network configuration policy.
 If you apply an incorrect configuration, you can use the following example to troubleshoot and correct the failed node network policy.
 
-In this example, a Linux bridge policy is applied to an example cluster that has three control plane nodes (master) and three compute (worker) nodes.
+In this example, a Linux bridge policy is applied to an example cluster that has three control plane nodes and three compute nodes.
 The policy fails to be applied because it references an incorrect interface.
 To find the error, investigate the available NMState resources. You can then update the policy with the correct configuration.
 
@@ -83,7 +82,7 @@ The output shows that the policy failed on all nodes:
 .Example output
 [source,terminal]
 ----
-NAME                                   STATUS
+NAME                                         STATUS
 control-plane-1.ens01-bridge-testfail        FailedToConfigure
 control-plane-2.ens01-bridge-testfail        FailedToConfigure
 control-plane-3.ens01-bridge-testfail        FailedToConfigure
@@ -201,7 +200,7 @@ The output shows that the interface name on the nodes is `ens1` but the failed p
 [source,yaml]
 ----
    - ipv4:
- ...
+...
       name: ens1
       state: up
       type: ethernet