diff --git a/modules/creating-an-infra-node.adoc b/modules/creating-an-infra-node.adoc
index 2e4e7ec1ae..58be6f2389 100644
--- a/modules/creating-an-infra-node.adoc
+++ b/modules/creating-an-infra-node.adoc
@@ -41,7 +41,7 @@ $ oc get nodes
 ====
 If the default node selector key conflicts with the key of a pod's label, then the default node selector is not applied.
 
-However, do not set a default node selector that might cause a pod to become unschedulable. For example, setting the default node selector to a specific node role, such as `node-role.kubernetes.io/infra=""`, when a pod's label is set to a different node role, such as `node-role.kubernetes.io/master=""`, can cause the pod to become unschedulable. For this reason, it is not recommended to set the default node selector to specific node roles.
+However, do not set a default node selector that might cause a pod to become unschedulable. For example, setting the default node selector to a specific node role, such as `node-role.kubernetes.io/infra=""`, when a pod's label is set to a different node role, such as `node-role.kubernetes.io/master=""`, can cause the pod to become unschedulable. For this reason, use caution when setting the default node selector to specific node roles.
 
 You can alternatively use a project node selector to avoid cluster-wide node selector key conflicts.
 ====
@@ -63,10 +63,10 @@ metadata:
   name: cluster
 ...
 spec:
-  defaultNodeSelector: node-role.kubernetes.io/app= <1>
+  defaultNodeSelector: topology.kubernetes.io/zone=us-east-1 <1>
 ...
 ----
-<1> This example node selector deploys pods on app nodes by default.
+<1> This example node selector deploys pods on nodes in the `us-east-1` zone by default.
 
 .. Save the file to apply the changes.