troubleshooting table formatting with right nav ui bug

modules/ROOT/nav.adoc

@@ -2,26 +2,28 @@
 * xref:introduction.adoc[]
 * xref:components.adoc[]
 * xref:faqs.adoc[]
-* Preliminary steps
-** xref:preliminary-steps.adoc[]
+* xref:preliminary-steps.adoc[]
 ** xref:feasibility-checklists.adoc[]
 ** xref:deployment-infrastructure.adoc[]
 ** xref:create-target.adoc[]
 ** xref:rollback.adoc[]
-* Phase 1: Deploy {zdm-proxy} and connect client applications
-** xref:phase1.adoc[]
+//phase 1
+* xref:phase1.adoc[]
 ** xref:setup-ansible-playbooks.adoc[]
 ** xref:deploy-proxy-monitoring.adoc[]
 ** xref:tls.adoc[]
 ** xref:connect-clients-to-proxy.adoc[]
 ** xref:metrics.adoc[]
 ** xref:manage-proxy-instances.adoc[]
-* Phase 2: Migrate and validate data
-** xref:migrate-and-validate-data.adoc[]
+//phase 2
+* xref:migrate-and-validate-data.adoc[]
 ** xref:cassandra-data-migrator.adoc[]
 ** xref:dsbulk-migrator.adoc[]
+//phase 3
 * xref:enable-async-dual-reads.adoc[]
+//phase 4
 * xref:change-read-routing.adoc[]
+//phase 5
 * xref:connect-clients-to-target.adoc[]
 * Troubleshooting
 ** xref:troubleshooting.adoc[]

modules/ROOT/pages/cassandra-data-migrator.adoc

@@ -193,7 +193,7 @@ Use {cstar-data-migrator} to identify large fields from a table that may break y
 [[cdm-connection-params]]
 === Common connection parameters for Origin and Target
 
-[cols="3,1,3"]
+[cols="3,1,3",width="75%"]
 |===
 |Property | Default | Notes
 
@@ -243,7 +243,7 @@ Use {cstar-data-migrator} to identify large fields from a table that may break y
 [[cdm-origin-schema-params]]
 === Origin schema parameters
 
-[cols="3,1,3a"]
+[cols="3,1,3a",width="75%"]
 |===
 |Property | Default | Notes
 
@@ -286,7 +286,7 @@ For optimization reasons, {cstar-data-migrator} does not migrate TTL and writeti
 [[cdm-target-schema-params]]
 === Target schema parameter
 
-[cols="3,1,3"]
+[cols="3,1,3",width=75%]
 |===
 |Property | Default | Notes
 
@@ -304,7 +304,7 @@ Auto-correction parameters allow {cstar-data-migrator} to correct data differenc
 
 For information about invoking `DiffData` in a {cstar-data-migrator} command, see xref:#cdm-validation-steps[{cstar-data-migrator} steps in validation mode] in this topic.
 
-[cols="3,1,3a"]
+[cols="3,1,3a",width=75%]
 |===
 |Property | Default | Notes
 
@@ -336,7 +336,7 @@ The `TIMESTAMP` of records may have an effect. If the `WRITETIME` of the Origin
 
 Performance and operations parameters that can affect migration throughput, error handling, and similar concerns.
 
-[cols="3,1,3"]
+[cols="3,1,3",width=75%]
 |===
 |Property | Default | Notes
 
@@ -386,7 +386,7 @@ Parameters to perform schema transformations between Origin and Target.
 
 By default, these parameters are commented out.
 
-[cols="3,1,3a"]
+[cols="3,1,3a",width=75%]
 |===
 |Property | Default | Notes
 
@@ -438,7 +438,7 @@ Cassandra filters are applied on the coordinator node. Note that, depending on t
 
 By default, these parameters are commented out.
 
-[cols="3,1,3"]
+[cols="3,1,3",width=75%]
 |===
 |Property | Default | Notes
 
@@ -464,7 +464,7 @@ Java filters are applied on the client node. Data must be pulled from the Origin
 
 By default, these parameters are commented out.
 
-[cols="3,1,3"]
+[cols="3,1,3",width=75%]
 |===
 |Property | Default | Notes
 
@@ -501,7 +501,7 @@ If used, the `spark.cdm.feature.constantColumns.names`, `spark.cdm.feature.const
 
 By default, these parameters are commented out.
 
-[cols="3,1,3"]
+[cols="3,1,3",width=75%]
 |===
 |Property | Default | Notes
 
@@ -531,7 +531,7 @@ The explode map feature allows you convert an Origin table Map into multiple Tar
 
 By default, these parameters are commented out.
 
-[cols="3,1,3"]
+[cols="3,1,3",width=75%]
 |===
 |Property | Default | Notes
 
@@ -558,7 +558,7 @@ The Guardrail job will generate a report; other jobs will skip records that exce
 
 By default, these parameters are commented out.
 
-[cols="3,1,3"]
+[cols="3,1,3",width=75%]
 |===
 |Property | Default | Notes
 
@@ -577,7 +577,7 @@ Note that a secure connect bundle (SCB) embeds these details.
 
 By default, these parameters are commented out.
 
-[cols="3,1,3"]
+[cols="3,1,3",width=75%]
 |===
 |Property | Default | Notes
 

modules/ROOT/pages/connect-clients-to-proxy.adoc

@@ -89,7 +89,7 @@ This means that, if your {zdm-proxy} is configured with an Origin or Target clus
 * If Origin requires authentication but Target does not, your client application must supply credentials for Origin.
 * If neither cluster requires authentication, no credentials are needed.
 
-[cols="1,1,1"]
+[cols="1,1,1",width=75%]
 |===
 |Auth enabled on Origin
 |Auth enabled on Target

modules/ROOT/pages/dsbulk-migrator.adoc

@@ -94,7 +94,7 @@ for which to generate DDL statements.
 The following options are available for the `migrate-live` command. Most options have sensible default values and do not
 need to be specified, unless you want to override the default value.
 
-[cols="2,8,14"]
+[cols="2,8,14",width=75%]
 |===
 
 | `-c`
@@ -297,7 +297,7 @@ The following options are available for the `generate-script` command.
 Most options have sensible default values and do not need to be specified, unless you want to override the default value.
 
 
-[cols="2,8,14"]
+[cols="2,8,14",width=75%]
 |===
 
 | `-c` 
@@ -469,7 +469,7 @@ Case-sensitive table names must be entered in their exact case.
 The following options are available for the `generate-ddl` command. 
 Most options have sensible default values and do not need to be specified, unless you want to override the default value.
 
-[cols="2,8,14"]
+[cols="2,8,14",width=75%]
 |===
 
 | `-a`