diff --git a/README.md b/README.md
index a2771efa6..564bb68a1 100644
--- a/README.md
+++ b/README.md
@@ -17,8 +17,9 @@ pipelines with no access to Kubernetes directly.
 
 * Rolling updates on Postgres cluster changes
 * Volume resize without Pod restarts
+* Database connection pooler
 * Cloning Postgres clusters
-* Logical Backups to S3 Bucket
+* Logical backups to S3 Bucket
 * Standby cluster from S3 WAL archive
 * Configurable for non-cloud environments
 * UI to create and edit Postgres cluster manifests
diff --git a/docs/user.md b/docs/user.md
index 69e885b5d..4a99b1078 100644
--- a/docs/user.md
+++ b/docs/user.md
@@ -514,7 +514,7 @@ executed.
 
 ## Connection pooler
 
-The operator can create a database side connection pooler for those applications,
+The operator can create a database side connection pooler for those applications
 where an application side pooler is not feasible, but a number of connections is
 high. To create a connection pooler together with a database, modify the
 manifest:
@@ -526,22 +526,21 @@ spec:
 
 This will tell the operator to create a connection pooler with default
 configuration, through which one can access the master via a separate service
-`{cluster-name}-pooler`. In most of the cases provided default configuration
-should be good enough.
-
-To configure a new connection pooler, specify:
+`{cluster-name}-pooler`. In most of the cases the
+[default configuration](reference/operator_parameters.md#connection-pool-configuration)
+should be good enough. To configure a new connection pooler individually for
+each Postgres cluster, specify:
 
 ```
 spec:
   connectionPooler:
     # how many instances of connection pooler to create
-    number_of_instances: 2
+    numberOfInstances: 2
 
     # in which mode to run, session or transaction
     mode: "transaction"
 
-    # schema, which operator will create to install credentials lookup
-    # function
+    # schema, which operator will create to install credentials lookup function
     schema: "pooler"
 
     # user, which operator will create for connection pooler
@@ -557,13 +556,17 @@ spec:
         memory: 100Mi
 ```
 
-By default `pgbouncer` is used to create a connection pooler. To find out about
-pooler modes see [docs](https://www.pgbouncer.org/config.html#pooler_mode) (but
-it should be general approach between different implementation).
+The `enableConnectionPooler` flag is not required when the `connectionPooler`
+section is present in the manifest. But, it can be used to disable/remove the
+pooler while keeping its configuration.
 
-Note, that using `pgbouncer` means meaningful resource CPU limit should be less
-than 1 core (there is a way to utilize more than one, but in K8S it's easier
-just to spin up more instances).
+By default, `pgbouncer` is used as connection pooler. To find out about pooler
+modes read the `pgbouncer` [docs](https://www.pgbouncer.org/config.html#pooler_mode)
+(but it should be the general approach between different implementation).
+
+Note, that using `pgbouncer` a meaningful resource CPU limit should be 1 core
+or less (there is a way to utilize more than one, but in K8s it's easier just to
+spin up more instances).
 
 ## Custom TLS certificates
 
diff --git a/manifests/complete-postgres-manifest.yaml b/manifests/complete-postgres-manifest.yaml
index 3e69f07b0..07733a5db 100644
--- a/manifests/complete-postgres-manifest.yaml
+++ b/manifests/complete-postgres-manifest.yaml
@@ -87,7 +87,7 @@ spec:
 #  - Sat:00:00-04:00
 
   connectionPooler:
-    number_of_instances: 2
+    numberOfInstances: 2
     mode: "transaction"
     schema: "pooler"
     user: "pooler"