diff --git a/operators/admin/olm-restricted-networks.adoc b/operators/admin/olm-restricted-networks.adoc
index 94bb2f6f77..0b324e9ccf 100644
--- a/operators/admin/olm-restricted-networks.adoc
+++ b/operators/admin/olm-restricted-networks.adoc
@@ -22,14 +22,17 @@ After enabling OLM in a restricted network, you can continue to use your unrestr
 
 [IMPORTANT]
 ====
-While OLM can manage Operators from local sources, the ability for a given Operator to run successfully in a restricted network still depends on the Operator itself. The Operator must:
+While OLM can manage Operators from local sources, the ability for a given Operator to run successfully in a restricted network still depends on the Operator itself meeting the following criteria:
 
 * List any related images, or other container images that the Operator might require to perform their functions, in the `relatedImages` parameter of its `ClusterServiceVersion` (CSV) object.
 * Reference all specified images by a digest (SHA) and not by a tag.
 
-You can search on the Red Hat Ecosystem Catalog for a list of Red Hat Operators that support running in disconnected mode by selecting the *Disconnected* filter under *Infrastucture Features*:
+You can search software on the link:https://catalog.redhat.com/software/search?p=1&deployed_as=Operator&type=Containerized%20application&badges_and_features=Disconnected[Red Hat Ecosystem Catalog] for a list of Red Hat Operators that support running in disconnected mode by filtering with the following selections:
 
-link:https://catalog.redhat.com/software/operators/search[]
+[horizontal]
+Type:: Containerized application
+Deployment method:: Operator
+Infrastructure features:: Disconnected
 ====
 
 [role="_additional-resources"]