Fixed some warnings

aiven · Nov 10, 2022 · 365ef63 · 365ef63
1 parent 1ff5274
commit 365ef63
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 5 deletions.
diff --git a/docs/platform/howto/manage-vpc-peering.rst b/docs/platform/howto/manage-vpc-peering.rst
@@ -16,7 +16,7 @@ To set up VPC peering for your Aiven project:
    .. note::
        You'll need either an **admin** or an **operator** user role to be able to create a VPC. For more information about Aiven project members and roles, refer to :doc:`../concepts/projects_accounts_access`.  
 
-4. Enter the IP range that you want to use for the VPC connection.  Use an IP range that does not overlap with any networks that you want to connect via VPC peering. For example, if your own networks use the range 10.0.0.0/8, you could set the range for your Aiven project's VPC to 192.168.0.0/24.
+4. Enter the IP range that you want to use for the VPC connection.  Use an IP range that does not overlap with any networks that you want to connect via VPC peering. For example, if your own networks use the range `10.0.0.0/8`, you could set the range for your Aiven project's VPC to `192.168.0.0/24`.
 
 5. Click **Create VPC**.
 

diff --git a/docs/products/kafka/kafka-connect/howto/couchbase-sink.rst b/docs/products/kafka/kafka-connect/howto/couchbase-sink.rst
@@ -50,7 +50,7 @@ Define the connector configurations in a file (we'll refer to it with the name `
         "couchbase.password": "COUCHBASE_PASSWORD",
         "couchbase.bucket": "COUCHBASE_BUCKET",
         "topics": "TOPIC_LIST"
-}
+    }
 
 The configuration file contains the following entries:
 

diff --git a/docs/products/kafka/kafka-connect/howto/couchbase-source.rst b/docs/products/kafka/kafka-connect/howto/couchbase-source.rst
@@ -59,7 +59,7 @@ Define the connector configurations in a file (we'll refer to it with the name `
         "couchbase.collections": "COUCHBASE_COLLECTIONS",
         "couchbase.source.handler": "com.couchbase.connect.kafka.handler.source.RawJsonSourceHandler",
         "value.converter": "org.apache.kafka.connect.converters.ByteArrayConverter",
-}
+    }
 
 The configuration file contains the following entries:
 

diff --git a/docs/products/mysql/howto/create-tables-without-primary-keys.rst b/docs/products/mysql/howto/create-tables-without-primary-keys.rst
@@ -7,9 +7,8 @@ If you Aiven for MySQL was created after 2020-06-03, then by default your Aiven
 #. On the **Overview** tab, in the **Advanced configuration** section, click **Change**.
 #. Find the ``mysql.sql_require_primary_key`` parameter.
 
-If you ``mysql.sql_require_primary_key`` is enabled, then your Aiven for MySQL does not allow to create new tables without primary keys. When this ``mysql.sql_require_primary_key`` is enabled, you won't be able to create tables without primary keys. You will get the following error message:
+If you ``mysql.sql_require_primary_key`` is enabled, then your Aiven for MySQL does not allow to create new tables without primary keys. When this ``mysql.sql_require_primary_key`` is enabled, you won't be able to create tables without primary keys. You will get the following error message::
 
-.. code::
     Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.
 
 If creating tables without primary keys is prevented and the table that you're trying to create is known to be small you may override this setting and create the table anyway.