DOC-5898, DOC-5851, DOC-5826 Pre-migration syntax prep

modules/ROOT/nav.adoc

@@ -1,29 +1,29 @@
 .Get started
-* xref:pulsarInstall.adoc[]
-* xref:pulsarQuickStart.adoc[]
-* xref:cfgRefPulsarDseConnection.adoc[]
+* xref:ROOT:pulsarInstall.adoc[]
+* xref:ROOT:pulsarQuickStart.adoc[]
+* xref:ROOT:cfgRefPulsarDseConnection.adoc[]
 
 .Map topics to tables
-* xref:cfgRefPulsarDseTable.adoc[]
-* xref:cfgPulsarDisplayingTopic.adoc[]
-* xref:cfgPulsarMapKeyPair.adoc[]
-* xref:cfgPulsarMapJson.adoc[]
-* xref:cfgPulsarMapAvroMessages.adoc[]
-* xref:cfgPulsarMapUdt.adoc[]
-* xref:cfgPulsarCqlQuery.adoc[]
-* xref:cfgPulsarMapMultipleTables.adoc[]
-* xref:cfgPulsarMultTopicToTables.adoc[]
+* xref:ROOT:cfgRefPulsarDseTable.adoc[]
+* xref:ROOT:cfgPulsarDisplayingTopic.adoc[]
+* xref:ROOT:cfgPulsarMapKeyPair.adoc[]
+* xref:ROOT:cfgPulsarMapJson.adoc[]
+* xref:ROOT:cfgPulsarMapAvroMessages.adoc[]
+* xref:ROOT:cfgPulsarMapUdt.adoc[]
+* xref:ROOT:cfgPulsarCqlQuery.adoc[]
+* xref:ROOT:cfgPulsarMapMultipleTables.adoc[]
+* xref:ROOT:cfgPulsarMultTopicToTables.adoc[]
 
 .Operations
-* xref:opsPulsarAboutOperations.adoc[]
-* xref:opsPulsarScaling.adoc[]
-* xref:opsPulsarChangeSchema.adoc[]
-* xref:opsPulsarDeleteConnector.adoc[]
-* xref:monPulsarConnectMetrics.adoc[]
+* xref:ROOT:opsPulsarAboutOperations.adoc[]
+* xref:ROOT:opsPulsarScaling.adoc[]
+* xref:ROOT:opsPulsarChangeSchema.adoc[]
+* xref:ROOT:opsPulsarDeleteConnector.adoc[]
+* xref:ROOT:monPulsarConnectMetrics.adoc[]
 
 .Troubleshooting
-* xref:trbPulsarTsLargeBatches.adoc[]
-* xref:cfgPulsarConfigureErrorHandling.adoc[]
+* xref:ROOT:trbPulsarTsLargeBatches.adoc[]
+* xref:ROOT:cfgPulsarConfigureErrorHandling.adoc[]
 
 .Release notes
 * https://github.com/datastax/release-notes/blob/master/DataStax_Apache_Pulsar_Connector_1.4_Release_Notes.md[Release notes]

modules/ROOT/pages/cfgPulsarMapAvroMessages.adoc

@@ -40,7 +40,7 @@ The {pulsar-short} topic name is `users_topic` and have the following records:
 
 The value field uses the following Avro Schema:
 
-[source,java]
+[source,json]
 ----
 {
  "namespace": "example.avro",

modules/ROOT/pages/cfgPulsarMapJson.adoc

@@ -104,7 +104,7 @@ cqlsh -e "CREATE KEYSPACE stocks_keyspace \
   'Cassandra': 1};"
 ----
 +
-For {dse-short} and {cass-short} clusters, make sure that the keyspace is replicated to a datacenter set in the {product-short}'s `xref:cfgRefPulsarDseConnection.adoc[contactPoints]` parameter.
+For {dse-short} and {cass-short} clusters, make sure that the keyspace is replicated to a datacenter set in the {product-short}'s `xref:ROOT:cfgRefPulsarDseConnection.adoc[contactPoints]` parameter.
 {dse-short} datacenter names are case sensitive.
 Use `xref:dse:managing:tools/nodetool/ring.adoc[nodetool ring]` to get a list of datacenters.
 
@@ -133,7 +133,7 @@ For example, this command verifies the schema for `stocks_keyspace`:
 nodetool describering -- stocks_keyspace
 ----
 
-. In the {product-short} configuration file, add the {pulsar-short} topic name to `xref:cfgRefPulsarDseTable.adoc#topics[topics]`, and define the xref:cfgRefPulsarDseTable.adoc#mapping[field-to-column mapping].
+. In the {product-short} configuration file, add the {pulsar-short} topic name to `xref:ROOT:cfgRefPulsarDseTable.adoc#topics[topics]`, and define the xref:ROOT:cfgRefPulsarDseTable.adoc#mapping[field-to-column mapping].
 +
 The following example is maps the `stocks_topic` to the `stocks_table` using the minimum required settings:
 +
@@ -308,7 +308,7 @@ cqlsh -e "CREATE KEYSPACE stocks_keyspace \
   'Cassandra': 1};"
 ----
 +
-For {dse-short} and {cass-short} clusters, make sure that the keyspace is replicated to a datacenter set in the {product-short}'s `xref:cfgRefPulsarDseConnection.adoc[contactPoints]` parameter.
+For {dse-short} and {cass-short} clusters, make sure that the keyspace is replicated to a datacenter set in the {product-short}'s `xref:ROOT:cfgRefPulsarDseConnection.adoc[contactPoints]` parameter.
 {dse-short} datacenter names are case sensitive.
 Use `xref:dse:managing:tools/nodetool/ring.adoc[nodetool ring]` to get a list of datacenters.
 
@@ -337,7 +337,7 @@ For example, this command verifies the schema for `stocks_keyspace`:
 nodetool describering -- stocks_keyspace
 ----
 
-. In the {product-short} configuration file, add the {pulsar-short} topic name to `xref:cfgRefPulsarDseTable.adoc#topics[topics]`, and then define the xref:cfgRefPulsarDseTable.adoc#mapping[field-to-column mapping].
+. In the {product-short} configuration file, add the {pulsar-short} topic name to `xref:ROOT:cfgRefPulsarDseTable.adoc#topics[topics]`, and then define the xref:ROOT:cfgRefPulsarDseTable.adoc#mapping[field-to-column mapping].
 +
 The following example is maps the `stocks_topic` to the `stocks_table` using the minimum required settings:
 +

modules/ROOT/pages/cfgPulsarMapKeyPair.adoc

@@ -30,7 +30,7 @@ cqlsh -e "CREATE KEYSPACE world_keyspace \
   'Cassandra': 1};"
 ----
 +
-For {dse-short} and {cass-short} clusters, make sure that the keyspace is replicated to a datacenter set in the {product-short}'s `xref:cfgRefPulsarDseConnection.adoc[contactPoints]` parameter.
+For {dse-short} and {cass-short} clusters, make sure that the keyspace is replicated to a datacenter set in the {product-short}'s `xref:ROOT:cfgRefPulsarDseConnection.adoc[contactPoints]` parameter.
 {dse-short} datacenter names are case sensitive.
 Use `xref:dse:managing:tools/nodetool/ring.adoc[nodetool ring]` to get a list of datacenters.
 
@@ -52,7 +52,7 @@ For example, this command verifies the schema for `world_keyspace`:
 nodetool describering -- world_keyspace
 ----
 
-. In the {product} configuration file, add the {pulsar-short} topic name to `xref:cfgRefPulsarDseTable.adoc#topics[topics]`, and define the xref:cfgRefPulsarDseTable.adoc#mapping[field-to-column mapping].
+. In the {product} configuration file, add the {pulsar-short} topic name to `xref:ROOT:cfgRefPulsarDseTable.adoc#topics[topics]`, and define the xref:ROOT:cfgRefPulsarDseTable.adoc#mapping[field-to-column mapping].
 +
 The following example is maps the `world_topic` to the `world_table` using the minimum required settings:
 +

modules/ROOT/pages/cfgPulsarMapMultipleTables.adoc

@@ -134,7 +134,7 @@ topic:
 +
 [source,yaml]
 ----
-“topic:
+topic:
    stocks_topic:
       stocks_keyspace:
          stocks_table_by_exchange:

modules/ROOT/pages/cfgPulsarMapUdt.adoc

@@ -167,7 +167,7 @@ If your mapping includes maps or UDTs, you can xref:ROOT:cfgPulsarCqlQuery.adoc[
 
 When a new record arrives, the {product-short} sets only the non-null fields in the message.
 It won't override UDT fields that have a null value or aren't present in the {pulsar-short} record.
-This configuration requires that `xref:cfgRefPulsarDseTable.adoc#nullToUnset[nullToUnset]` is `true`.
+This configuration requires that `xref:ROOT:cfgRefPulsarDseTable.adoc#nullToUnset[nullToUnset]` is `true`.
 
 This configuration helps minimize tombstones in the database.
 It uses the CQL `UPDATE` command to only update the fields present in the {pulsar-short} record.

modules/ROOT/pages/cfgPulsarMultTopicToTables.adoc

@@ -137,11 +137,9 @@ a|
 ----
 |===
 
-Map the topics into different keyspaces and tables, `stocks_keyspace.stocks_table` and `baseball_keyspace.baseball_table`.
+Map the topics into different keyspaces and tables, `stocks_keyspace.stocks_table` and `baseball_keyspace.baseball_table`:
 
-The {company} Schema definitions:
-
-* {blank}
+* {company} Schema definitions:
 +
 [source,cql]
 ----
@@ -154,8 +152,6 @@ CREATE TABLE stocks_keyspace.stocks_table_by_symbol (
    value double,
    PRIMARY KEY (symbol, ts));
 ----
-
-* {blank}
 +
 [source,cql]
 ----
@@ -168,26 +164,22 @@ CREATE TABLE baseball_keyspace.baseball_table (
    city text);
 ----
 
-In the {product-short} configuration, add the following settings:
-
-* {blank}
+* {product-short} configuration settings:
 +
-[source,console]
+[source,yaml]
 ----
 topic:
    stocks_topic:
       stocks_keyspace:
          stocks_table_by_symbol:
             mapping: 'symbol=value.symbol, ts=value.dateTime, exchange=value.exchange, industry=value.industry, name=key.name, value=value.value'
 ----
-
-* {blank}
 +
-[source,console]
+[source,yaml]
 ----
 topic:
    baseball_topic:
       baseball_keyspace:
          baseball_table:
             mapping: 'team=key, number=value.number, firstname=value.firstname, lastname=value.lastname, street=value.street, city=value.city'
-----
+----