fix build errors and warnings

docs/modules/integrate/pages/cdc-connectors.adoc

@@ -230,7 +230,7 @@ Each database type has its own database type-to-struct type mappings. For specif
 |io.debezium.time.Date|java.time.LocalDate / java.util.Date / String `yyyy-MM-dd`
 |io.debezium.time.Time|java.time.Duration / String ISO-8601 `PnDTnHnMn.nS`
 
-.5+|INT64
+.6+|INT64
 |-|long/Long
 |io.debezium.time.Timestamp|java.time.Instant / String `yyyy-MM-dd HH:mm:ss.SSS`
 |io.debezium.time.MicroTimestamp|java.time.Instant / String `yyyy-MM-dd HH:mm:ss.SSS`
@@ -243,6 +243,8 @@ Each database type has its own database type-to-struct type mappings. For specif
 |BOOLEAN|-|boolean/Boolean / String
 |STRING|-|String
 
+|===
+
 The `RecordPart#value` field contains Debezium's message in a JSON format. This JSON format uses string as date representation,
 instead of ints, which are standard in Debezium but harder to work with.
 
@@ -252,13 +254,11 @@ We strongly recommend using `time.precision.mode=adaptive` (default).
 Using `time.precision.mode=connect` uses `java.util.Date` to represent dates, time, etc. and is less precise.
 ====
 
-|===
-
 == Migration tips
 
 Hazelcast {open-source-product-name} has a Debezium CDC connector, but it's based on an older version of Debezium.
 Migration to the new connector is straightforward but be aware of the following changes:
 
  * You should use the `com.hazelcast.enterprise.jet.cdc` package instead of `com.hazelcast.jet.cdc`.
  * Artifact names are now `hazelcast-enterprise-cdc-debezium`, `hazelcast-enterprise-cdc-mysql` and `hazelcast-enterprise-cdc-postgres` (instead of `hazelcast-jet-...`).
- * Debezium renamed certain terms, which we have also replicated in our code. For example, `include list` replaces `whitelist`, `exclude list` replaces `blacklist`. This means, for example, you need to use `setTableIncludeList` instead of `setTableWhitelist`. For more detail on new Debezium names, see their link:https://debezium.io/documentation/reference/stable/connectors/mysql.html#mysql-connector-properties[MySQL] and link:https://debezium.io/documentation/reference/stable/connectors/postgresql.html#postgresql-connector-properties[PostgreSQL] documentation.
+ * Debezium renamed certain terms, which we have also replicated in our code. For example, `include list` replaces `whitelist`, `exclude list` replaces `blacklist`. This means, for example, you need to use `setTableIncludeList` instead of `setTableWhitelist`. For more detail on new Debezium names, see their link:https://debezium.io/documentation/reference/stable/connectors/mysql.html#mysql-connector-properties[MySQL] and link:https://debezium.io/documentation/reference/stable/connectors/postgresql.html#postgresql-connector-properties[PostgreSQL] documentation.

docs/modules/mapstore/pages/configuring-a-generic-maploader.adoc

@@ -35,11 +35,11 @@ NOTE: If you are using the slim distribution, you need to add `hazelcast-mapstor
 
 This example shows a basic map configuration that uses a data connection called `my-mysql-database`. See xref:data-structures:map.adoc[] for the details of other properties that you can include in your map configuration.
 
-[tabs] 
-==== 
-XML:: 
-+ 
--- 
+[tabs]
+====
+XML::
++
+--
 [source,xml]
 ----
 <hazelcast>
@@ -112,10 +112,10 @@ TIP: As well as these properties, you can also configure xref:configuration-guid
 a|`''` (empty)
 |
 
-[tabs] 
-==== 
-XML:: 
-+ 
+[tabs]
+====
+XML::
++
 --
 [source,xml]
 ----
@@ -130,8 +130,8 @@ XML::
 </hazelcast>
 ----
 --
-YAML:: 
-+ 
+YAML::
++
 --
 [source,yaml]
 ----
@@ -145,8 +145,8 @@ hazelcast:
             data-connection-ref: my-mysql-database
 ----
 --
-Java:: 
-+ 
+Java::
++
 --
 [source,java]
 ----
@@ -167,10 +167,10 @@ mapConfig.setMapStoreConfig(mapStoreConfig);
 a|The name of the map.
 |
 
-[tabs] 
-==== 
-XML:: 
-+ 
+[tabs]
+====
+XML::
++
 --
 [source,xml]
 ----
@@ -186,8 +186,8 @@ XML::
 </hazelcast>
 ----
 --
-YAML:: 
-+ 
+YAML::
++
 --
 [source,yaml]
 ----
@@ -202,8 +202,8 @@ hazelcast:
             external-name: test
 ----
 --
-Java:: 
-+ 
+Java::
++
 --
 [source,java]
 ----
@@ -225,10 +225,10 @@ mapConfig.setMapStoreConfig(mapStoreConfig);
 a|The SQL connector is derived from the data connection in the configuration.
 |
 
-[tabs] 
-==== 
-XML:: 
-+ 
+[tabs]
+====
+XML::
++
 --
 [source,xml]
 ----
@@ -244,8 +244,8 @@ XML::
 </hazelcast>
 ----
 --
-YAML:: 
-+ 
+YAML::
++
 --
 [source,yaml]
 ----
@@ -260,8 +260,8 @@ hazelcast:
             mapping-type: JDBC
 ----
 --
-Java:: 
-+ 
+Java::
++
 --
 [source,java]
 ----
@@ -283,10 +283,10 @@ mapConfig.setMapStoreConfig(mapStoreConfig);
 |id
 |
 
-[tabs] 
-==== 
-XML:: 
-+ 
+[tabs]
+====
+XML::
++
 --
 [source,xml]
 ----
@@ -302,8 +302,8 @@ XML::
 </hazelcast>
 ----
 --
-YAML:: 
-+ 
+YAML::
++
 --
 [source,yaml]
 ----
@@ -318,8 +318,8 @@ hazelcast:
             id-column: id
 ----
 --
-Java:: 
-+ 
+Java::
++
 --
 [source,java]
 ----
@@ -342,10 +342,10 @@ the table. Missing columns must have a default value defined.
 |
 |
 
-[tabs] 
-==== 
-XML:: 
-+ 
+[tabs]
+====
+XML::
++
 --
 [source,xml]
 ----
@@ -361,8 +361,8 @@ XML::
 </hazelcast>
 ----
 --
-YAML:: 
-+ 
+YAML::
++
 --
 [source,yaml]
 ----
@@ -377,8 +377,8 @@ hazelcast:
             columns: name
 ----
 --
-Java:: 
-+ 
+Java::
++
 --
 [source,java]
 ----
@@ -394,7 +394,7 @@ mapConfig.setMapStoreConfig(mapStoreConfig);
 --
 ====
 
-|[[columns]]`type-name`
+|[[type-name]]`type-name`
 |The type name of the compact GenericRecord. Use this property to map your record to an existing domain class.
 
 |

docs/modules/sql/pages/mapping-to-jdbc.adoc

@@ -85,7 +85,7 @@ Create the mapping.
 
 ```sql
 CREATE MAPPING people
-DATA CONNECTION 'mysql-database'
+DATA CONNECTION 'mysql-database' <1>
 ```
 
 <1> The name of the data connection configuration on your members.