Fix source language on code blocks

Author: eric-schneider

docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarColumnWritetimeTimestamp.adoc

@@ -6,7 +6,7 @@ In the Apache Pulsar(TM) topic mapping, you can optionally specify which column
 The mapping setting provides a special property, `__timestamp`.
 The format is:
 
-[source,language-yaml]
+[source,yaml]
 ----
 topic:
   my_topic:
@@ -27,7 +27,7 @@ The connector will automatically transform it to the database's proper numeric t
 that is, to `MICROSECONDS`.
 Example:
 
-[source,language-yaml]
+[source,yaml]
 ----
 topic:
   my_topic:

docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarCqlQuery.adoc

@@ -8,7 +8,7 @@ NOTE: This feature is only meant for advanced use cases. Most often, you can use
 If used, you must provide the bound variables used in the query in the mapping column.
 For example, give the following query:
 
-[source,language-yaml]
+[source,yaml]
 ----
 topic:
   my_topic:
@@ -19,7 +19,7 @@ topic:
 
 The corresponding mapping in this example should be defined as:
 
-[source,language-yaml]
+[source,yaml]
 ----
 topic:
   my_topic:

docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarDisplayingTopic.adoc

@@ -7,7 +7,7 @@ https://pulsar.apache.org/docs/en/reference-cli-tools/#consume
 
 To show Apache Pulsar messages:
 
-[source,language-bash]
+[source,bash]
 ----
  bin/pulsar-client consume topic_name -s "subscription_name"
 ----
@@ -20,7 +20,7 @@ subscription_name:: Arbitrary name for the consumer subscription.
 
 You'll see the message data when a message is received:
 
-[source,no-highlight]
+[source,console]
 ----
 ----- got message -----
 key:[My key], properties:[], content:My content

docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarJsonMessageSchema.adoc

@@ -33,7 +33,7 @@ See the https://github.com/datastax/pulsar-examples/tree/master/producers/src/ma
 Ensure that keyspace is replicated to a datacenter that is set in the DataStax Apache Pulsar Connector xref:cfgRefPulsarDseConnection.adoc#contactPoints[contactPoints] parameter.
 For example, create the `stocks_keyspace`:
 +
-[source,language-bash]
+[source,bash]
 ----
 cqlsh -e "CREATE KEYSPACE stocks_keyspace \
   WITH replication = {'class': 'NetworkTopologyStrategy',\
@@ -45,7 +45,7 @@ Use https://docs.datastax.com/en/dse/6.8/dse-dev/datastax_enterprise/tools/nodet
 
 . Create the table. For example, create the `stocks_table`:
 +
-[source,language-bash]
+[source,bash]
 ----
 cqlsh -e "CREATE TABLE stocks_keyspace.stocks_table ( \
   symbol text, \
@@ -59,7 +59,7 @@ cqlsh -e "CREATE TABLE stocks_keyspace.stocks_table ( \
 
 . Verify that all nodes have the same schema version using https://docs.datastax.com/en/dse/6.8/dse-admin/datastax_enterprise/tools/nodetool/toolsDescribeRing.html[nodetool describering]. Replace keyspace\_name:
 +
-[source,language-bash]
+[source,bash]
 ----
 nodetool describering -- keyspace\_name
 ----
@@ -72,7 +72,7 @@ nodetool describering -- keyspace\_name
 +
 Example configurations for `stocks_topic` to `stocks_table` using the minimum required settings:
 +
-[source,language-yaml]
+[source,yaml]
 ----
 tasks.max: 1
 topics: stocks_topic

docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapAvroMessages.adoc

@@ -69,15 +69,15 @@ The DataStax keyspace name is `users_keyspace` and table is `users_table`.
 
 To create the table use the following command:
 
-[source,language-cql]
+[source,cql]
 ----
 CREATE TABLE users_keyspace.users_table (userid text primary key, name text,
           favoritenumber int, favoritecolor text);
 ----
 
 Configure the connector and use the following map specification:
 
-[source,language-yaml]
+[source,yaml]
 ----
 topic:
     users_topic:

docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapKeyPair.adoc

@@ -19,7 +19,7 @@ Null values are not allowed in PK columns.
 Ensure that keyspace is replicated to a datacenter that is set in the DataStax Apache Pulsar Connector xref:cfgRefPulsarDseConnection.adoc#contactPoints[contactPoints] parameter.
 For example, create the world_keyspace:
 +
-[source,language-bash]
+[source,bash]
 ----
 cqlsh -e "CREATE KEYSPACE world_keyspace WITH replication = {'class': 'NetworkTopologyStrategy','Cassandra': 1};"
 ----
@@ -29,14 +29,14 @@ Use https://docs.datastax.com/en/dse/6.8/dse-dev/datastax_enterprise/tools/nodet
 
 . Create the table. For example, create the world\_table:
 +
-[source,language-bash]
+[source,bash]
 ----
 cqlsh -e "CREATE TABLE world_table (recordid int PRIMARY KEY, continent text);"
 ----
 
 . Verify that all nodes have the same schema version using [nodetool describering](https://docs.datastax.com/en/dse/6.8/dse-admin/datastax_enterprise/tools/nodetool/toolsDescribeRing.html). Replace keyspace_name:
 +
-[source,language-bash]
+[source,bash]
 ----
 nodetool describering -- keyspace_name
 ----
@@ -48,7 +48,7 @@ nodetool describering -- keyspace_name
 +
 Example configurations for `world_topic` to `world_table` using the minimum required settings:
 +
-[source,language-yaml]
+[source,yaml]
 ----
 tasks.max: 1
 topics: world_topic

docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapMultipleTables.adoc

@@ -12,14 +12,14 @@ In the example `stocks_topic`, the key is a basic string and the value is regula
 |
 APPLE
 |
-[source,no-highlight]
+[source,console]
 ----
 {"symbol":"APPL", "value":208, "exchange":"NASDAQ", "industry":"TECH", "ts":"2018-11-26T19:26:27.483"}
 ----
 |
 EXXON MOBIL
 |
-[source,no-highlight]
+[source,console]
 ----
 {"symbol":"M",
 "value":80,
@@ -30,14 +30,14 @@ EXXON MOBIL
 |
 GENERAL MOTORS
 |
-[source,no-highlight]
+[source,console]
 ----
 {"symbol":"GM", "value":38, "exchange":"NYSE", "industry":"AUTO", "ts":"2018-11-26T19:26:27.483"}
 ----
 |
 AT&T
 |
-[source,no-highlight]
+[source,console]
 ----
 {"symbol":"AT&T",
 "value":33,
@@ -48,7 +48,7 @@ AT&T
 |
 FORD MOTOR
 |
-[source,no-highlight]
+[source,console]
 ----
 {"symbol":"F", "value":10, "exchange":"NYSE", "industry":"AUTO", "ts":"2018-11-26T19:26:27.483"}
 ----
@@ -59,7 +59,7 @@ In the DataStax keyspace `stocks_keyspace`, create three different tables that o
 
 * `stocks_table_by_symbol`
 +
-[source,language-cql]
+[source,cql]
 ----
 CREATE TABLE stocks_keyspace.stocks_table_by_symbol (
    symbol text,
@@ -73,7 +73,7 @@ CREATE TABLE stocks_keyspace.stocks_table_by_symbol (
 
 * `stocks_table_by_exhange`
 +
-[source,language-cql]
+[source,cql]
 ----
 CREATE TABLE stocks_keyspace.stocks_table_by_exchange (
    symbol text,
@@ -87,7 +87,7 @@ CREATE TABLE stocks_keyspace.stocks_table_by_exchange (
 
 * `stocks_table_by_industry`
 +
-[source,language-cql]
+[source,cql]
 ----
 CREATE TABLE stocks_keyspace.stocks_table_by_industry (
    symbol text,
@@ -103,7 +103,7 @@ Configure the connector and add all the map specifications:
 
 * `stocks_topic` to `stocks_table_by_symbol`
 +
-[source,language-yaml]
+[source,yaml]
 ----
 topic:
    stocks_topic:
@@ -114,7 +114,7 @@ topic:
 
 * `stocks_topic` to `stocks_table_by_exchange`
 +
-[source,language-yaml]
+[source,yaml]
 ----
 “topic:
    stocks_topic:
@@ -125,7 +125,7 @@ topic:
 
 * `stocks_topic` to `stocks_table_by_industry`
 +
-[source,language-yaml]
+[source,yaml]
 ----
 topic:
    stocks_topic:

docs-src/pulsar-sink-core/modules/ROOT/pages/cfgPulsarMapUdt.adoc

@@ -10,13 +10,13 @@ In the example `stocks_topic`, the key is a basic string and the value is regula
 |key|value
 
 |APPLE|
-[source,no-highlight]
+[source,console]
 ----
 {"symbol":"APPL", "value":208, "exchange":"NASDAQ", "industry":"TECH", "ts":"2018-11-26T19:26:27.483"}
 ----
 
 |EXXON MOBIL|
-[source,no-highlight]
+[source,console]
 ----
 {"symbol":"M",
 "value":80,
@@ -26,13 +26,13 @@ In the example `stocks_topic`, the key is a basic string and the value is regula
 ----
 
 |GENERAL MOTORS|
-[source,no-highlight]
+[source,console]
 ----
 {"symbol":"GM", "value":38, "exchange":"NYSE", "industry":"AUTO", "ts":"2018-11-26T19:26:27.483"}
 ----
 
 |AT&T|
-[source,no-highlight]
+[source,console]
 ----
 {"symbol":"AT&T",
 "value":33,
@@ -42,7 +42,7 @@ In the example `stocks_topic`, the key is a basic string and the value is regula
 ----
 
 |FORD MOTOR|
-[source,no-highlight]
+[source,console]
 ----
 {"symbol":"F", "value":10, "exchange":"NYSE", "industry":"AUTO", "ts":"2018-11-26T19:26:27.483"}
 ----
@@ -51,7 +51,7 @@ In the example `stocks_topic`, the key is a basic string and the value is regula
 
 The DataStax keyspace name is `stocks_keyspace`. In the stocks keyspace create the user defined type, `stocks_type`:
 
-[source,language-cql]
+[source,cql]
 ----
 CREATE TYPE stocks_keyspace.stocks_type (
     symbol text,
@@ -63,7 +63,7 @@ CREATE TYPE stocks_keyspace.stocks_type (
 
 Define a table named `stocks_udt_table` that has a column for the primitive string field `name` and a second column that uses the type, `stocks_type`:
 
-[source,language-cql]
+[source,cql]
 ----
 CREATE TABLE stocks_keyspace.stocks_table (
     name text primary key,
@@ -72,7 +72,7 @@ CREATE TABLE stocks_keyspace.stocks_table (
 
 Configure the connector settings and use the following for the map specification:
 
-[source,language-yaml]
+[source,yaml]
 ----
 topic:
     stocks_topic:
@@ -87,7 +87,7 @@ The DataStax Apache Pulsar(TM) Connector supports mapping complex user defined t
 
 The DataStax keyspace name is `stocks_keyspace`. In the stocks keyspace create the user defined type, `stocks_complex_type`:
 
-[source,language-cql]
+[source,cql]
 ----
 CREATE TYPE stocks_keyspace.stocks_complex_type (
     symbol text,
@@ -106,7 +106,7 @@ CREATE TYPE stocks_keyspace.stocks_complex_type (
 
 Define a table named `stocks_complex_udt_table` that has a column for the primitive string field `name` and a second column that uses the type, `stocks_complex_type`:
 
-[source,language-cql]
+[source,cql]
 ----
 CREATE TABLE stocks_keyspace.stocks_complex_udt_table (
     name text primary key,
@@ -115,7 +115,7 @@ CREATE TABLE stocks_keyspace.stocks_complex_udt_table (
 
 Configure the connector settings and use the following for the map specification:
 
-[source,language-yaml]
+[source,yaml]
 ----
 topic:
     stocks_topic: