diff --git a/docs/flowcollector-flows-netobserv-io-v1beta2.adoc b/docs/flowcollector-flows-netobserv-io-v1beta2.adoc
index 94c084b8b..8437741e1 100644
--- a/docs/flowcollector-flows-netobserv-io-v1beta2.adoc
+++ b/docs/flowcollector-flows-netobserv-io-v1beta2.adoc
@@ -94,7 +94,7 @@ Type::
 | `string`
 | `deploymentModel` defines the desired type of deployment for flow processing. Possible values are: +
 
-- `Direct` (default) to make the flow processor listen directly from the agents. +
+- `Direct` (default) to make the flow processor listen directly from the agents. Only recommended on small clusters, below 15 nodes. +
 
 - `Kafka` to make flows sent to a Kafka pipeline before consumption by the processor. +
 
@@ -2672,9 +2672,10 @@ configuration, you can disable it and install your own instead.
 
 | `enable`
 | `boolean`
-| Set `enable` to `true` to deploy network policies on the namespaces used by Network Observability (main and privileged). It is disabled by default.
-These network policies better isolate the Network Observability components to prevent undesired connections to them.
-This option is enabled by default, disable it to manually manage network policies
+| Deploys network policies on the namespaces used by Network Observability (main and privileged).
+These network policies better isolate the Network Observability components to prevent undesired connections from and to them.
+This option is enabled by default when using with OVNKubernetes, and disabled otherwise (it has not been tested with other CNIs).
+When disabled, you can manually create the network policies for the Network Observability components.
 
 |===
 == .spec.processor