cql shell to cqlsh in migration docs

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

@@ -13,7 +13,7 @@ We conclude by describing two sample client applications that serve as real-worl
 
 You can use the provided sample client applications, in addition to your own, as a quick way to validate that the deployed {product-proxy} is reading and writing data from the expected origin and target clusters.
 
-This topic also explains how to connect CQL shell (`cqlsh`) to {product-proxy}.
+This topic also explains how to connect `cqlsh` to {product-proxy}.
 
 == {company}-compatible drivers
 

modules/ROOT/pages/create-target.adoc

@@ -82,7 +82,7 @@ For more information, see xref:astra-db-serverless:cql:develop-with-cql.adoc[CQL
 To help you prepare the schema from the DDL in your origin cluster, consider using the `generate-ddl` functionality in the {dsbulk-migrator-repo}[{dsbulk-migrator}].
 However, this tool doesn't automatically convert MVs or indexes.
 
-CQL statements, such as those used to reproduce the schema on the target database, can be executed in {astra-db} using the built-in or standalone CQL shell (`cqlsh`).
+CQL statements, such as those used to reproduce the schema on the target database, can be executed in {astra-db} using the built-in or standalone `cqlsh`.
 For more information, see xref:astra-db-serverless:cql:develop-with-cql.adoc#connect-to-the-cql-shell[CQL for {astra-db}].
 
 == Using a generic CQL cluster as the target

modules/ROOT/pages/troubleshooting-tips.adoc

@@ -149,7 +149,7 @@ This flag will prevent you from accessing the logs when {product-proxy} stops or
 
 Querying `system.peers` and `system.local` can help you investigate {product-proxy} configuration issues:
 
-. xref:ROOT:connect-clients-to-proxy.adoc#connect-the-cql-shell-to-zdm-proxy[Connect CQL shell (`cqlsh`) to a {product-proxy} instance.]
+. xref:ROOT:connect-clients-to-proxy.adoc#connect-the-cql-shell-to-zdm-proxy[Connect cqlsh to a {product-proxy} instance.]
 
 . Query `system.peers`:
 +

modules/sideloader/partials/sideloader-partials.adoc

@@ -23,7 +23,7 @@ It is important to use the specific node name to ensure that each node has a uni
 // end::command-placeholders-common[]
 
 // tag::validate[]
-After the migration is complete, you can query the migrated data using the xref:astra-db-serverless:cql:develop-with-cql.adoc#connect-to-the-cql-shell[CQL shell] (`cqlsh`) or xref:astra-db-serverless:api-reference:row-methods/find-many.adoc[{data-api}].
+After the migration is complete, you can query the migrated data using the xref:astra-db-serverless:cql:develop-with-cql.adoc#connect-to-the-cql-shell[cqlsh] or xref:astra-db-serverless:api-reference:row-methods/find-many.adoc[{data-api}].
 
 You can xref:ROOT:cassandra-data-migrator.adoc#cdm-validation-steps[run {cass-migrator} ({cass-migrator-short}) in validation mode] for more thorough validation.
 {cass-migrator-short} also offers an AutoCorrect mode to reconcile any differences that it detects.