Use character replacements for trademarks

Author: eric-schneider

modules/ROOT/pages/index.adoc

@@ -48,7 +48,7 @@ xref:streaming-learning:use-cases-architectures:starlight/jms/index.adoc[Get sta
 .xref:streaming-learning:use-cases-architectures:starlight/kafka/index.adoc[Starlight for Kafka]
 ****
 --
-Starlight for Kafka brings native Apache Kafka® protocol support to Apache Pulsar by introducing a Kafka protocol handler on Pulsar brokers.
+Starlight for Kafka brings native Apache Kafka(R) protocol support to Apache Pulsar by introducing a Kafka protocol handler on Pulsar brokers.
 
 xref:streaming-learning:use-cases-architectures:starlight/kafka/index.adoc[Get started now] | xref:starlight-for-kafka:ROOT:index.adoc[Configuring] | https://github.com/datastax/starlight-for-kafka[Source Code]
 --

modules/pulsar-io/pages/connectors/index.adoc

@@ -2,7 +2,7 @@
 :navtitle: Connector Overview
 :page-tag: connectors,sinks,sources,astra-streaming,dev,develop,pulsar,go
 
-{product_name} offers fully-managed Apache Pulsar™ connectors.
+{product_name} offers fully-managed Apache Pulsar(TM) connectors.
 
 Create, monitor, and manage both source and sink connectors through our simple UI, the `pulsar-admin` CLI, or RESTful API. Connect popular data sources to Apache Pulsar topics or sink data from Pulsar topics to popular systems.
 

modules/use-cases-architectures/pages/change-data-capture/index.adoc

@@ -57,11 +57,11 @@ In the context of CDC there are a few schema configurations of note. All of thes
 
 == Cassandra change data capture (CDC) agent
 
-The Cassandra CDC agent is a process running on each node in a Cassandra cluster that watches for data changes on tables that have enabled the CDC feature. Using Cassandra’s https://cassandra.apache.org/doc/4.0/cassandra/configuration/cass_yaml_file.html#commitlog_sync[commitlog_sync option], the agent periodically syncs a separate log in a special “cdc_raw” directory. Each log entry is a CDC event. The CDC agent creates a new event message containing the row coordinates of the changed data and produces the message to a downstream Pulsar cluster. For more information about the agent, how to include its configuration in cassandra.yaml, and event data specifics read the "https://docs.datastax.com/en/cdc-for-cassandra/docs/latest/index.html[DataStax CDC for Apache Cassandra® Documentation]".
+The Cassandra CDC agent is a process running on each node in a Cassandra cluster that watches for data changes on tables that have enabled the CDC feature. Using Cassandra’s https://cassandra.apache.org/doc/4.0/cassandra/configuration/cass_yaml_file.html#commitlog_sync[commitlog_sync option], the agent periodically syncs a separate log in a special “cdc_raw” directory. Each log entry is a CDC event. The CDC agent creates a new event message containing the row coordinates of the changed data and produces the message to a downstream Pulsar cluster. For more information about the agent, how to include its configuration in cassandra.yaml, and event data specifics read the "https://docs.datastax.com/en/cdc-for-cassandra/docs/latest/index.html[DataStax CDC for Apache Cassandra(R) Documentation]".
 
 == Cassandra Source Connector for Apache Pulsar
 
-Each table that has CDC enabled also has a corresponding Source Connector in Pulsar. This is unlike the CDC agent where the process runs on each Cassandra node, keeping a log of all table changes. Each table-specific Source Connector subscribes to the events topic the agent is producing messages to. When the connector “sees” a message for its table, it uses the row coordinates within the message to retrieve the mutated data from Cassandra and create a new message with the specifics. That new message is written to a data topic where others can subscribe and receive CDC messages. For more information about the Cassandra Source Connector, its configuration, and how to create it read the "https://docs.datastax.com/en/cdc-for-cassandra/docs/latest/index.html[DataStax CDC for Apache Cassandra® Documentation]".
+Each table that has CDC enabled also has a corresponding Source Connector in Pulsar. This is unlike the CDC agent where the process runs on each Cassandra node, keeping a log of all table changes. Each table-specific Source Connector subscribes to the events topic the agent is producing messages to. When the connector “sees” a message for its table, it uses the row coordinates within the message to retrieve the mutated data from Cassandra and create a new message with the specifics. That new message is written to a data topic where others can subscribe and receive CDC messages. For more information about the Cassandra Source Connector, its configuration, and how to create it read the "https://docs.datastax.com/en/cdc-for-cassandra/docs/latest/index.html[DataStax CDC for Apache Cassandra(R) Documentation]".
 
 [discrete]
 === Event deduplication

modules/use-cases-architectures/pages/starlight/_index.adoc

@@ -6,7 +6,7 @@ The goal of all the extensions is to create a native, seamless interaction with
 
 == Starlight for Kafka
 
-Starlight for Kafka brings native Apache Kafka® protocol support to Apache Pulsar by introducing a Kafka protocol handler on Pulsar brokers.
+Starlight for Kafka brings native Apache Kafka(R) protocol support to Apache Pulsar by introducing a Kafka protocol handler on Pulsar brokers.
 
 xref:use-cases-architectures:starlight/kafka/index.adoc[Get started now] | xref:starlight-for-kafka:ROOT:index.adoc[Configuring] | https://github.com/datastax/starlight-for-kafka[Source Code]
 

modules/use-cases-architectures/pages/starlight/jms/index.adoc

@@ -4,7 +4,7 @@
 :page-tag: starlight-jms,dev,quickstart,pulsar,jms
 
 Starlight for JMS is a highly compliant JMS implementation designed to run on a modern streaming platform.
-This guide will get you up and running with a simple Java JMS client that can talk to an Apache Pulsar™ streaming instance.
+This guide will get you up and running with a simple Java JMS client that can talk to an Apache Pulsar(TM) streaming instance.
 
 == Prerequisites
 

modules/use-cases-architectures/pages/starlight/rabbitmq/index.adoc

@@ -2,7 +2,7 @@
 :navtitle: Starlight for RabbitMQ
 :description: Learn how to get started using the Starlight for RabbitMQ extension with Pulsar and get hands on by publishing and consuming messages from a topic.
 
-Starlight for RabbitMQ acts as a proxy between your https://www.rabbitmq.com/[RabbitMQ] application and https://pulsar.apache.org/[Apache Pulsar™] cluster.
+Starlight for RabbitMQ acts as a proxy between your https://www.rabbitmq.com/[RabbitMQ] application and https://pulsar.apache.org/[Apache Pulsar(TM)] cluster.
 It implements the AMQP 0.9.1 protocol used by RabbitMQ clients and translates AMQP frames and concepts to Pulsar concepts.
 
 If source code is your thing, visit the https://github.com/datastax/starlight-for-rabbitmq[project's repo on GitHub].