fixes

docs/platform/howto/reactivate-suspended-project.rst

@@ -3,9 +3,11 @@ Reactivate suspended projects
 
 If you have bills past due and didn't set up a payment method, you may receive this error when trying to log in to the console:
 
-  ERROR
+.. code::
 
-  Project suspended, access prohibited
+   ERROR
+
+   Project suspended, access prohibited
 
 Reactivate a suspended project
 ------------------------------

docs/products/postgresql/reference/use-of-deprecated-tls-versions.rst

@@ -29,7 +29,7 @@ To check the TLS versions clients are connecting with, you can query the ``pg_st
 
 .. code::
 
-     datname  │   pid   │ usesysid │ usename  │ application_name │  client_addr   │ ssl │ version │         cipher         │         backend_start         
+    datname   │   pid   │ usesysid │ usename  │ application_name │  client_addr   │ ssl │ version │         cipher         │         backend_start         
     ──────────┼─────────┼──────────┼──────────┼──────────────────┼────────────────┼─────┼─────────┼────────────────────────┼───────────────────────────────
     defaultdb │ 2172508 │    16412 │ avnadmin │ psql             │ 192.178.0.1    │ t   │ TLSv1.3 │ TLS_AES_256_GCM_SHA384 │ 2022-09-12 12:39:12.644646+00
 

docs/products/postgresql/troubleshooting/troubleshooting-connection-pooling.rst

@@ -10,18 +10,15 @@ PgBouncer is a lightweight connection pooler for PostgreSQL® with low memory re
 
 PgBouncer offers several methods when rotating connections:
 
-Session pooling
-    This is the most permissive method. When a client connects, it gets assigned with a server connection that is maintained as long as the client stays connected. When the client disconnects, the server connection is put back into the pool. This mode supports all PostgreSQL features.
+- **Session pooling:** This is the most permissive method. When a client connects, it gets assigned with a server connection that is maintained as long as the client stays connected. When the client disconnects, the server connection is put back into the pool. This mode supports all PostgreSQL features.
 
-Transaction pooling
-  A server connection is assigned to a client only during a transaction. When PgBouncer notices that the transaction is over, the server connection is put back into the pool.
+- **Transaction pooling:** A server connection is assigned to a client only during a transaction. When PgBouncer notices that the transaction is over, the server connection is put back into the pool.
 
   .. warning::
 
-    This mode breaks a few session-based features of PostgreSQL. Use it only when the application cooperates without using the features that break. For incompatible features, see `PostgreSQL feature map for pooling modes <https://www.pgbouncer.org/features>`_.
+     This mode breaks a few session-based features of PostgreSQL. Use it only when the application cooperates without using the features that break. For incompatible features, see `PostgreSQL feature map for pooling modes <https://www.pgbouncer.org/features>`_.
 
-Statement pooling
-  This is the most restrictive method, which disallows multi-statement transactions. This is meant to enforce the ``autocommit`` mode on the client and is mostly targeted at PL/Proxy.
+- **Statement pooling:** This is the most restrictive method, which disallows multi-statement transactions. This is meant to enforce the ``autocommit`` mode on the client and is mostly targeted at PL/Proxy.
 
 Handling connection pooling issues
 ----------------------------------

docs/tools/terraform/howto/update-deprecated-resources.rst

@@ -9,21 +9,21 @@ Use the following steps to migrate from resources that have been deprecated or r
 In the following example, the ``aiven_database`` field is migrated to the new ``aiven_pg_database`` field for an Aiven for PostgreSQL® service. 
 
 1. Replace references to the deprecated field with the new field. In the following file ``aiven_database`` was replaced with ``aiven_pg_database``:
-
-.. code::
-
-    - resource "aiven_database" "mydatabase" {
-        project       = aiven_project.myproject.project
-        service_name  = aiven_pg.mypg.service_name
-        database_name = "<DATABASE_NAME>"
-    }
-
-
-    + resource "aiven_pg_database" "mydatabase" {
-        project       = aiven_project.myproject.project
-        service_name  = aiven_pg.mypg.service_name
-        database_name = "<DATABASE_NAME>"
-    }
+   
+   .. code::
+   
+       - resource "aiven_database" "mydatabase" {
+           project       = aiven_project.myproject.project
+           service_name  = aiven_pg.mypg.service_name
+           database_name = "<DATABASE_NAME>"
+       }
+   
+   
+       + resource "aiven_pg_database" "mydatabase" {
+           project       = aiven_project.myproject.project
+           service_name  = aiven_pg.mypg.service_name
+           database_name = "<DATABASE_NAME>"
+       }
 
 2. View a list of all resources in the state file:
 

docs/tools/terraform/howto/upgrade-to-opensearch.rst

@@ -12,48 +12,48 @@ To upgrade an existing Elasticsearch service to OpenSearch using Terraform:
 Use the following steps to complete the upgrade safely:
 
 1. Change the ``elasticsearch_version = 7`` to ``opensearch_version = 1``. This is the equivalent to clicking the migrate button in the console.
-
-.. code-block::
-
-    # Existing Elasticsearch Resource
-    resource "aiven_elasticsearch" "es" {
-      project = "project-name"
-      cloud_name = "google-us-east4"
-      plan = "business-4"
-      service_name = "es"
-
-      elasticsearch_user_config {
-        elasticsearch_version = 7
-      }
-    }
-
-.. code-block::
-
-    # Modified Elasticsearch Resource, upgrades to OpenSearch v1
-    resource "aiven_elasticsearch" "es" {
-      project = "project-name"
-      cloud_name = "google-us-east4"
-      plan = "business-4"
-      service_name = "es"
-
-      elasticsearch_user_config {
-        opensearch_version = 1
-      }
-    }
-
-Once you have updated your configuration, check that the change looks correct:
-
-.. code::
-
-   terraform plan
-
-Apply the upgrade:
-
-.. code::
-
-   terraform apply
-
-Your service will now upgrade to OpenSearch, and if you view it in the web console, it will show as an OpenSearch service.
+   
+   .. code-block::
+   
+       # Existing Elasticsearch Resource
+       resource "aiven_elasticsearch" "es" {
+         project = "project-name"
+         cloud_name = "google-us-east4"
+         plan = "business-4"
+         service_name = "es"
+   
+         elasticsearch_user_config {
+           elasticsearch_version = 7
+         }
+       }
+   
+   .. code-block::
+   
+       # Modified Elasticsearch Resource, upgrades to OpenSearch v1
+       resource "aiven_elasticsearch" "es" {
+         project = "project-name"
+         cloud_name = "google-us-east4"
+         plan = "business-4"
+         service_name = "es"
+   
+         elasticsearch_user_config {
+           opensearch_version = 1
+         }
+       }
+   
+   Once you have updated your configuration, check that the change looks correct:
+   
+   .. code::
+   
+      terraform plan
+   
+   Apply the upgrade:
+   
+   .. code::
+   
+      terraform apply
+   
+   Your service will now upgrade to OpenSearch, and if you view it in the web console, it will show as an OpenSearch service.
 
 2. After the migration you will need to remove the Elasticsearch service from the Terraform state.
 
@@ -76,11 +76,11 @@ Your service will now upgrade to OpenSearch, and if you view it in the web conso
         }
       }
 
-Bring the Terraform state back in sync with your OpenSearch service by importing the service.
+4. Bring the Terraform state back in sync with your OpenSearch service by importing the service.
 
-.. code-block::
-
-   terraform import 'aiven_opensearch.os' <project-name>/<service-name>
+   .. code-block::
+   
+      terraform import 'aiven_opensearch.os' <project-name>/<service-name>
 
 Your Elasticsearch service has been upgraded to OpenSearch with Terraform, and the resource configuration updated to use a resource type of OpenSearch.