Remove page aliases

Author: eric-schneider

modules/ROOT/pages/index.adoc

@@ -1,19 +1,18 @@
 = About Starlight for JMS
 :navtitle: Starlight for JMS
 :page-tag: starlight-jms,planner,dev,admin,pulsar,jms
-:page-aliases: docs@starlight-jms::index.adoc,
 
 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.
 
 == Key Features
 
 Starlight for JMS key features include:
 
-* *Blazing fast JMS performance*: Achieve 1 million JMS messages per second with 99 percentile publish to acknowledge latency of less than 10 ms. 
+* *Blazing fast JMS performance*: Achieve 1 million JMS messages per second with 99 percentile publish to acknowledge latency of less than 10 ms.
 * *Drop-in replacement for existing JMS applications*: Supports JMS/Jakarta 2.0 and is backwards compatible with JMS 1.1. 100% pass rate on JMS compliance test for supported features.
 * *Horizontally scalable JMS*: Apache Pulsar is a horizontally scaled distributed streaming platform. You can scale up or down without operational hassles. Pulsar separates compute from storage, which means you can scale those dimensions independently, as required. Pulsar supports offloading old data to object storage for practically infinite storage capacity.
-* *Reduced total cost of ownership*: Because Apache Pulsar is natively multi-tenant and high performance, you can consolidate JMS applications spread across multiple legacy JMS brokers onto a single Apache Pulsar installation. And since Pulsar is easily horizontally scaled, you don’t need to overprovision. 
-* *Future proof*: Apache Pulsar can support traditional messaging workloads, but it can also support modern streaming use cases such as log collection, microservices integration, event streaming, event sourcing. New workloads can run alongside Legacy JMS applications. 
+* *Reduced total cost of ownership*: Because Apache Pulsar is natively multi-tenant and high performance, you can consolidate JMS applications spread across multiple legacy JMS brokers onto a single Apache Pulsar installation. And since Pulsar is easily horizontally scaled, you don’t need to overprovision.
+* *Future proof*: Apache Pulsar can support traditional messaging workloads, but it can also support modern streaming use cases such as log collection, microservices integration, event streaming, event sourcing. New workloads can run alongside Legacy JMS applications.
 * *Open source to avoid lock in*: Starlight for JMS and Apache Pulsar are 100% open source. You can run on-premise, in any cloud provider, or in Kubernetes.
 * *Adds message replay to JMS*: Apache Pulsar natively supports message retention and replay. This allows applications using Fast JMS for Apache Pulsar to travel back in time and replay previously consumed messages to recover from misconfiguration issues, recover from bugs in application code, and test new applications against real data.
 

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

@@ -1,5 +1,4 @@
 = Starlight for JMS FAQs
-
 :page-tag: starlight-jms,planner,dev,admin,pulsar,jms
 
 Answers to the (arguably) most common Starlight for JMS questions.

modules/examples/pages/pulsar-jms-batch-ack.adoc

@@ -1,5 +1,4 @@
 = Batch index acknowledgement
-:page-aliases: docs@starlight-jms::pulsar-jms-batch-ack.adoc
 
 Starlight for JMS improves acknowledgement of batched messages by supporting the tracking of 'ack' status by *batch index*. +
 

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

@@ -1,7 +1,5 @@
 = Starlight for JMS implementation details
-
 :page-tag: starlight-jms,dev,pulsar,jms
-:page-aliases: docs@starlight-jms::pulsar-jms-implementation.adoc
 
 A discussion of design and implementation decisions made to support JMS requirements.
 

modules/examples/pages/pulsar-jms-server-side-filters.adoc

@@ -1,5 +1,4 @@
 = Enabling server-side filters
-:page-aliases: docs@starlight-jms::pulsar-jms-server-side-filters.adoc
 
 Starlight for JMS offers *server-side filtering*, which executes JMS filtering features on the Pulsar Broker instead of the Client. +
 Previously, filtering was implemented with `jms.enableClientSideEmulation=true` on the Client side, which meant the Client application received all messages, even if they didn't match the filter. This caused inefficient network, CPU, and memory usage.
@@ -20,7 +19,7 @@ The `.nar` file filter is packaged with Luna Streaming *2.10.03+* and also avail
 +
 [NOTE]
 ====
-The path for the .nar is relative to your Pulsar directory.  
+The path for the .nar is relative to your Pulsar directory.
 ====
 For more, see xref:jms-migration:pulsar-jms-quickstart-sa.adoc[Standalone quick start].
 
@@ -61,7 +60,7 @@ In this case, the server-side filter applies both to JMS queues and JMS topics.
 
 [NOTE]
 ====
-If you set `jms.selector` on the subscription **and** set a message selector on the JMS client, the conditions on the subscription **and** the JMS client will both be fulfilled. 
+If you set `jms.selector` on the subscription **and** set a message selector on the JMS client, the conditions on the subscription **and** the JMS client will both be fulfilled.
 ====
 
 == Limitations

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

@@ -1,7 +1,6 @@
 = Installing Starlight for JMS
-
 :page-tag: starlight-jms,install,dev,admin,pulsar,jms,java,maven
-:page-aliases: docs@starlight-jms::pulsar-jms-install.adoc
+
 == Compatibility
 
 Wire protocol changes introduced in *Pulsar 2.9* can cause compatibility issues when using *Transactions*. +

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

@@ -1,7 +1,5 @@
 = Starlight for JMS standalone quick start
-
 :page-tag: starlight-jms,dev,quickstart,pulsar,java,jms
-:page-aliases: docs@starlight-jms::pulsar-jms-quickstart-sa.adoc
 
 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:
 

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

@@ -1,7 +1,5 @@
 = Mapping Pulsar concepts to JMS specifications
-
 :page-tag: starlight-jms,planner,dev,admin,pulsar,jms
-:page-aliases: docs@starlight-jms::pulsar-jms-mappings.adoc
 
 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.
 
@@ -137,7 +135,7 @@ Or modify the Pulsar broker's `broker.conf` file:
 allowAutoSubscriptionCreation=false
 ----
 
-If both `allowAutoSubscriptionCreation` and `jms.precreateQueueSubscription` are set to `false`, automatic subscription creation is completely disabled. 
+If both `allowAutoSubscriptionCreation` and `jms.precreateQueueSubscription` are set to `false`, automatic subscription creation is completely disabled.
 
 [#consumer-mappings]
 == Mappings between JMS consumer modes and Pulsar
@@ -153,7 +151,7 @@ There are five consumer mode session objects in JMS. This section describes how
 [#auto-ack]
 === Session.AUTO_ACKNOWLEDGE
 
-This mode maps to the Pulsar `acknowledgeMessage` API. 
+This mode maps to the Pulsar `acknowledgeMessage` API.
 
 By default, acknowledgements in Pulsar are asynchronous and best effort, enabling duplicates to always be displayed on the Consumer.
 
@@ -195,7 +193,7 @@ public class JMSExample {
                         public void onMessage(Message message) {
                             try {
                                 System.out.println("received " + message.getBody(String.class));
- 
+
                             } catch (Exception err) {
                                 err.printStackTrace();
                             }
@@ -223,7 +221,7 @@ public class JMSExample {
 [#dups-ok]
 === Session.DUPS_OK_ACKNOWLEDGE
 
-This mode maps to `Consumer.acknowledgeAsync()` without waiting for the `CompleteableFuture` returned by the method to complete. 
+This mode maps to `Consumer.acknowledgeAsync()` without waiting for the `CompleteableFuture` returned by the method to complete.
 
 Starlight for JMS logs an error in case there is something wrong, but the application will continue running and is not aware of the failure.
 
@@ -265,7 +263,7 @@ public class JMSExample {
                         public void onMessage(Message message) {
                             try {
                                 System.out.println("received " + message.getBody(String.class));
- 
+
                             } catch (Exception err) {
                                 err.printStackTrace();
                             }

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

@@ -1,7 +1,5 @@
 = Starlight for JMS configuration reference
-
 :page-tag: starlight-jms,dev,admin,manage,pulsar,jms
-:page-aliases: docs@starlight-jms::pulsar-jms-reference.adoc
 
 A complete configuration reference for Starlight for JMS.
 
@@ -29,7 +27,7 @@ factory.close();
 
 Configuration information can be passed when a `JMSContext` or `Session` is created with `JMSContext.createContext` or `Session.createSession`.
 
-Create a `PulsarConnectionFactory` with `initialContext` for configuration. 
+Create a `PulsarConnectionFactory` with `initialContext` for configuration.
 
 [source,language-java]
 ----
@@ -68,18 +66,18 @@ Other entries are ignored.
 [width="100%",cols="3,1,1,2,4"]
 
 |===
-| Configuration Entry | Required | Type | Default value | Notes 
+| Configuration Entry | Required | Type | Default value | Notes
 
 | `ackTimeout`
 | no
 | long
 | Disabled
-| Set timeout for unacked messages. Must be >1 second. 
+| Set timeout for unacked messages. Must be >1 second.
 
 | `ackTimeoutMillis`
 | no
 | long
-| 
+|
 | Same as `ackTimeout`, but expressed in milliseconds
 
 | `brokerServiceUrl`