OCPBUGS-47532: Added note to the nw-operator-cr file

Author: dfitzmau

modules/nw-network-config.adoc

@@ -37,6 +37,6 @@ Set the `networking.machineNetwork` to match the Classless Inter-Domain Routing
 The CIDR range `172.17.0.0/16` is reserved by `libVirt`. You cannot use any other CIDR range that overlaps with the `172.17.0.0/16` CIDR range for networks in your cluster.
 ====
 
-Phase 2:: After creating the manifest files by running `openshift-install create manifests`, you can define a customized Cluster Network Operator manifest with only the fields you want to modify. You can use the manifest to specify advanced network configuration.
+Phase 2:: After creating the manifest files by running `openshift-install create manifests`, you can define a customized Cluster Network Operator manifest with only the fields you want to modify. You can use the manifest to specify an advanced network configuration.
 
 During phase 2, you cannot override the values that you specified in phase 1 in the `install-config.yaml` file. However, you can customize the network plugin during phase 2.

modules/nw-operator-cr.adoc

@@ -117,6 +117,11 @@ The fields for this object specify the kube-proxy configuration.
 If you are using the OVN-Kubernetes cluster network plugin, the kube-proxy configuration has no effect.
 |====
 
+[IMPORTANT]
+====
+For a cluster that needs to deploy objects across multiple networks, ensure that you specify the same value for the `clusterNetwork.hostPrefix` parameter for each network type that is defined in the `install-config.yaml` file. Setting a different value for each `clusterNetwork.hostPrefix` parameter can impact the OVN-Kubernetes network plugin, where the plugin cannot effectively route object traffic among different nodes.
+====
+
 [discrete]
 [id="nw-operator-cr-defaultnetwork_{context}"]
 === defaultNetwork object configuration