mulesoft · glenn-rodgers-sf · May 5, 2026
@@ -3,7 +3,7 @@ ifndef::env-site,env-github[]
 include::_attributes.adoc[]
 endif::[]
 
-When a policy definition asset is published in Exchange, the asset details page displays a *Pending* flag next to *Implementations* in the left navigation bar. The flag indicates that the policy implementation has not been added. Add the policy implementation files to the policy definition to enable the policy to be available in runtime. The required implementation files are a binary file such as a WebAssembly (WASM) file for Flex Gateway or JAR for Mule 4 runtime and a YAML metadata file. 
+When a policy definition asset is published in Exchange, the asset details page displays a *Pending* flag next to *Implementations* in the left navigation bar. The flag indicates that the policy implementation has not been added. Add the policy implementation files to the policy definition to enable the policy to be available in runtime. The required implementation files are a binary file such as a WebAssembly (WASM) file for Omni Gateway or JAR for Mule 4 runtime and a YAML metadata file. 
 
 Before adding the policy implementation files, ensure that the policy definition asset is in the Stable state.
 

@@ -104,7 +104,7 @@ image::ex-search-spec-and-pages.png["Search results for the term ruleset highlig
 
 == View Instances
 
-View the instances of APIs and other assets in the *Instances* list on the asset details page. Instances are managed or unmanaged (non-managed). Managed instances are managed in API Manager. For example, when you register an API in API Manager, it creates a managed instance. This instance is linked to a specific runtime (like Mule Gateway or Anypoint Flex Gateway). Its environments (sandbox and production) appear automatically in the *Instances* list. The list includes the instance name, version, environment, URL, visibility, and whether an agent instance is verified via GoDaddy Agent Naming Service (ANS).
+View the instances of APIs and other assets in the *Instances* list on the asset details page. Instances are managed or unmanaged (non-managed). Managed instances are managed in API Manager. For example, when you register an API in API Manager, it creates a managed instance. This instance is linked to a specific runtime (like Mule Gateway or Anypoint Omni Gateway). Its environments (sandbox and production) appear automatically in the *Instances* list. The list includes the instance name, version, environment, URL, visibility, and whether an agent instance is verified via GoDaddy Agent Naming Service (ANS).
 
 Unmanaged (external) instances run outside Anypoint Platform. These instances are primarily for discovery—helping your team find all APIs in one catalog even if they aren’t governed in API Manager.
 

@@ -74,12 +74,12 @@ From the asset details page in Exchange, manage the implementation versions of a
 
 == Update Policy Implementations
 
-To update policy implementations to be compatible with your Flex Gateway version:
+To update policy implementations to be compatible with your Omni Gateway version:
 
 . Go to the *Policies* page.
 . Under *Applied policy status*, you'll see the policies that need updating. Click the more options menu icon and click *Check for implementation updates*.
 . The newest policy implementation compatible with your current version shows. +
-An error message will show if you have no policy implementations compatible with your current Flex Gateway version. See https://docs.mulesoft.com/exchange/add-policy-implementation-files-to-published-policy-definition[Add Policy Implementation Files to Published Policy Definition] for more info.
+An error message will show if you have no policy implementations compatible with your current Omni Gateway version. See https://docs.mulesoft.com/exchange/add-policy-implementation-files-to-published-policy-definition[Add Policy Implementation Files to Published Policy Definition] for more info.
 . In the confirmation dialog box, click *Update all*.
 + 
 The policy displays under *API-level policies*.