Use character replacements for trademarks

Author: eric-schneider

modules/ROOT/pages/index.adoc

@@ -2,7 +2,7 @@
 :navtitle: Starlight for JMS
 :page-tag: starlight-jms,planner,dev,admin,pulsar,jms
 
-Starlight for JMS is the first highly compliant JMS implementation designed to run on a modern streaming platform. It allows enterprises to take advantage of the scalability and resiliency of a modern streaming platform to run their existing JMS applications. Because Apache Pulsar™ is open-source and cloud-native, Starlight for JMS enables enterprises to move their JMS applications to run on-premises and in any cloud environment.
+Starlight for JMS is the first highly compliant JMS implementation designed to run on a modern streaming platform. It allows enterprises to take advantage of the scalability and resiliency of a modern streaming platform to run their existing JMS applications. Because Apache Pulsar(TM) is open-source and cloud-native, Starlight for JMS enables enterprises to move their JMS applications to run on-premises and in any cloud environment.
 
 == Key Features
 

modules/ROOT/pages/pulsar-jms-faq.adoc

@@ -6,13 +6,13 @@ Answers to the (arguably) most common Starlight for JMS questions.
 
 == What is the pricing for Starlight for JMS?
 
-Starlight for JMS is free open-source software. Enterprise support is available through https://www.datastax.com/products/luna-streaming[Luna Streaming], the DataStax commercial support offering for Apache Pulsar™.
+Starlight for JMS is free open-source software. Enterprise support is available through https://www.datastax.com/products/luna-streaming[Luna Streaming], the DataStax commercial support offering for Apache Pulsar(TM).
 
 == How is Starlight for JMS licensed?
 
 Starlight for JMS is licensed under https://www.apache.org/licenses/LICENSE-2.0.txt[Apache version 2.0].
 
-== How can I use Starlight for JMS in a JakartaEE® or JavaEE® application?
+== How can I use Starlight for JMS in a JakartaEE(R) or JavaEE(R) application?
 
 You can use the `resourceAdapter` {jms_repo}blob/master/resource-adapter[here].
 
@@ -47,9 +47,9 @@ IMPORTANT: Globally unique subscription names are not supported so the correspon
 
 We've provided the following integration examples:
 
-* {jms_repo}blob/master/examples/spring[Spring Boot®]
-* {jms_repo}blob/master/examples/payara-micro[Payara Micro®]
-* {jms_repo}blob/master/resource-adapter-tests[Apache TomEE®]
+* {jms_repo}blob/master/examples/spring[Spring Boot(R)]
+* {jms_repo}blob/master/examples/payara-micro[Payara Micro(R)]
+* {jms_repo}blob/master/resource-adapter-tests[Apache TomEE(R)]
 
 == How can I build Starlight for JMS from source?
 

modules/examples/pages/pulsar-jms-implementation.adoc

@@ -124,7 +124,7 @@ There are also specific behaviors mandates regarding these APIs:
 
 Starlight for JMS implements its own concurrent processing model in order to obey the specs, but it cannot use the built-in facilities provider by the Pulsar client.
 
-For `CompletionListeners`, which are useful for asynchronous sending of messages, Starlight for JMS relies on the Apache Pulsar™ asynchronous API, but there are some behaviors that are yet to be enforced with respect to `Session/JMSContext.close()`.
+For `CompletionListeners`, which are useful for asynchronous sending of messages, Starlight for JMS relies on the Apache Pulsar(TM) asynchronous API, but there are some behaviors that are yet to be enforced with respect to `Session/JMSContext.close()`.
 
 [#message-properties]
 == Message properties
@@ -146,7 +146,7 @@ Both of those features can be emulated on the client side with the following lim
 * For shared subscriptions, especially on queues, the message is discarded on the client and is "negative acknowledged" in order to let other consumers receive the message.
 * For `QueueBrowsers`, the message is discarded on the client side.
 
-Currently, the implementation of message selectors is based on Apache ActiveMQ® Java client classes, which are imported as a dependency in Starlight for JMS.
+Currently, the implementation of message selectors is based on Apache ActiveMQ(R) Java client classes, which are imported as a dependency in Starlight for JMS.
 
 NOTE: Apache ActiveMQ is licensed under Apache 2.0.
 
@@ -215,7 +215,7 @@ Map<String, Object> properties = new HashMap<>();
 [#unsupported-features]
 == Unsupported and emulated features
 
-The JMS 2.0 specifications describes broadly a generic messaging service and defines many interfaces and services. Apache Pulsar® does not support all of the required features, and Starlight for JMS is a wrapper over the Apache Pulsar Client.
+The JMS 2.0 specifications describes broadly a generic messaging service and defines many interfaces and services. Apache Pulsar(R) does not support all of the required features, and Starlight for JMS is a wrapper over the Apache Pulsar Client.
 
 Most of the features that are not natively supported by Pulsar are emulated by Starlight for JMS, which helps in porting existing JMS based applications.
 

modules/jms-migration/pages/pulsar-jms-install.adoc

@@ -23,7 +23,7 @@ Install Starlight for JMS by adding the following dependency to your Java Maven
 </dependency>
 ----
 
-That file contains only Starlight for JMS code and transitively imports the Apache Pulsar™ client and the Jakarta JMS 2.0 specifications JAR.
+That file contains only Starlight for JMS code and transitively imports the Apache Pulsar(TM) client and the Jakarta JMS 2.0 specifications JAR.
 
 You can also use a "fat" JAR that includes all dependencies:
 

modules/jms-migration/pages/pulsar-jms-quickstart-sa.adoc

@@ -1,7 +1,7 @@
 = Starlight for JMS standalone quickstart
 :page-tag: starlight-jms,dev,quickstart,pulsar,java,jms
 
-This quick start will get you up and running with a simple command-line Java JMS client that can talk to a local Apache Pulsar™ installation. The client:
+This quick start will get you up and running with a simple command-line Java JMS client that can talk to a local Apache Pulsar(TM) installation. The client:
 
 . Initializes a Starlight for JMS queue.
 . Attaches a message listener to that queue.
@@ -11,7 +11,7 @@ This quick start will get you up and running with a simple command-line Java JMS
 
 * https://maven.apache.org/install.html[Apache Maven]
 * https://openjdk.java.net/install/[Java OpenJDK 8 or 11]
-* A local installation of Apache Pulsar™, either the https://pulsar.apache.org/ja/download/[download binary] or a docker instance.
+* A local installation of Apache Pulsar(TM), either the https://pulsar.apache.org/ja/download/[download binary] or a docker instance.
 +
 IMPORTANT: If you choose an existing local Pulsar installation, make sure the Pulsar endpoints are \http://localhost:8080 and \http://localhost:6650, otherwise you'll need to modify the initialization properties in the example.
 
@@ -60,7 +60,7 @@ We'll use Apache Maven to handle dependency management so you don't have to manu
   <artifactId>pulsar-fast-jms-example</artifactId> <1>
   <packaging>jar</packaging>
   <version>1.0</version>
-  <name>DataStax Fast JMS for Apache Pulsar (R) example</name>
+  <name>DataStax Fast JMS for Apache Pulsar(R) example</name>
   <description>A simple JMS client designed to test the DataStax Fast JMS for Apache Pulsar library.</description>
   <properties>
     <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

modules/reference/pages/pulsar-jms-mappings.adoc

@@ -1,7 +1,7 @@
 = Mapping Pulsar concepts to JMS specifications
 :page-tag: starlight-jms,planner,dev,admin,pulsar,jms
 
-JMS specifications are built upon the concepts of *Topics* and *Queues*, but Apache Pulsar™ has only a general concept of *Topics* that can model both of those two domains.
+JMS specifications are built upon the concepts of *Topics* and *Queues*, but Apache Pulsar(TM) has only a general concept of *Topics* that can model both of those two domains.
 
 In Pulsar there is no concept of a queue: Starlight for JMS *treats Pulsar topics as queues when queue-related JMS API are in use*. There is no strict, cluster wide, verification that you are accessing a JMS Queue using the Topic API or vice versa.