diff --git a/docs/features/postgresql/index.mdx b/docs/features/postgresql/index.mdx
index a485f148e..9355e2e12 100644
--- a/docs/features/postgresql/index.mdx
+++ b/docs/features/postgresql/index.mdx
@@ -34,7 +34,7 @@ To learn how to use the Intents Operator and Credentials Operator to enforce acc
 
 ### How does Otterize work with PostgreSQL?
 
-Otterize Cloud will create a unique PostgreSQL username-password combination for each service's use, exposed via a Kubernetes Secret. The service will use these credentials to connect to the database. `ClientIntents` will define the access required by that service. As the intents are applied, Otterize Cloud will keep the database's list of users and GRANTs up to date so that the service is able to access it.
+The Otterize credentials operator will create a unique PostgreSQL username-password combination for each service's use, exposed via a Kubernetes Secret. The service will use these credentials to connect to the database. `ClientIntents` will define the access required by that service. As the intents are applied, The Otterize intents operator will keep the database's list of users and GRANTs up to date so that the service is able to access it.
 
 1. To get started, your cluster must have Otterize deployed.
 2. You'll need to create a `PostgreSQLServerConfig` in your cluster, providing a connection URL and admin-level credentials for Otterize to manage permissions in your database. Below is an example `PostgreSQLServerConfig` resource.