Address review, add ConnectionPool init for sync

docs/reference/cluster_manifest.md

@@ -152,7 +152,7 @@ These parameters are grouped directly under  the `spec` key in the manifest.
 * enableConnectionPool
   Tells the operator to create a connection pool with a database. If this
   field is true, a connection pool deployment will be created even if
-  `connectionPool` section is empty.
+  `connectionPool` section is empty. Optional, not set by default.
 
 ## Postgres parameters
 
@@ -376,7 +376,7 @@ present.
   How many instances of connection pool to create.
 
 * **mode**
-  In which mode to run connection pool, transaction or section.
+  In which mode to run connection pool, transaction or session.
 
 * **schema**
   Schema to create for credentials lookup function.

docs/reference/operator_parameters.md

@@ -613,7 +613,7 @@ operator being able to provide some reasonable defaults.
   Docker image to use for connection pool deployment.
 
 * **connection_pool_mode**
-  Default pool mode, sesssion or transaction.
+  Default pool mode, session or transaction.
 
 * **connection_pool_default_cpu_request**
   **connection_pool_default_memory_reques**

docs/user.md

@@ -468,7 +468,7 @@ spec:
 ```
 
 This will tell the operator to create a connection pool with default
-configuration, though which one can access the master via a separate service
+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.