GEODE-8839: Remove unneeded links from docs pages (#5912)
Co-authored-by: Karen Miller <millerka@vmware.com>
diff --git a/geode-docs/developing/events/configure_client_server_event_messaging.html.md.erb b/geode-docs/developing/events/configure_client_server_event_messaging.html.md.erb
index 427702f..9166d61 100644
--- a/geode-docs/developing/events/configure_client_server_event_messaging.html.md.erb
+++ b/geode-docs/developing/events/configure_client_server_event_messaging.html.md.erb
@@ -72,10 +72,3 @@
4. To have events enqueued for your clients during client downtime, configure durable client/server messaging.
5. Write any continuous queries (CQs) that you want to run to receive continuously streaming updates to client queries. CQ events do not update the client cache. If you have dependencies between CQs and/or interest registrations, so that you want the two types of subscription events to arrive as closely together on the client, use a single server pool for everything. Using different pools can lead to time differences in the delivery of events because the pools might use different servers to process and deliver the event messages.
-- **[Configuring Highly Available Servers](configuring_highly_available_servers.html)**
-
-- **[Implementing Durable Client/Server Messaging](implementing_durable_client_server_messaging.html)**
-
-- **[Tuning Client/Server Event Messaging](tune_client_server_event_messaging.html)**
-
-
diff --git a/geode-docs/developing/events/configuring_highly_available_servers.html.md.erb b/geode-docs/developing/events/configuring_highly_available_servers.html.md.erb
index d78221d..6dff04d 100644
--- a/geode-docs/developing/events/configuring_highly_available_servers.html.md.erb
+++ b/geode-docs/developing/events/configuring_highly_available_servers.html.md.erb
@@ -50,6 +50,3 @@
| > 0 | Sets the precise number of secondary servers to use for backup to the primary. |
| -1 | Every server that is not the primary is to be used as a secondary. |
-- **[Highly Available Client/Server Event Messaging](ha_event_messaging_whats_next.html)**
-
-
diff --git a/geode-docs/developing/events/tune_client_server_event_messaging.html.md.erb b/geode-docs/developing/events/tune_client_server_event_messaging.html.md.erb
index b4a1558..e7a0c2a 100644
--- a/geode-docs/developing/events/tune_client_server_event_messaging.html.md.erb
+++ b/geode-docs/developing/events/tune_client_server_event_messaging.html.md.erb
@@ -28,10 +28,3 @@
The client’s message tracking list holds the highest sequence ID of any message received for each originating thread. The list can become quite large in systems where there are many different threads coming and going and doing work on the cache. After a thread dies, its tracking entry is not needed. To avoid maintaining tracking information for threads that have died, the client expires entries that have had no activity for more than the `subscription-message-tracking-timeout`.
-- **[Conflate the Server Subscription Queue](conflate_server_subscription_queue.html)**
-
-- **[Limit the Server's Subscription Queue Memory Use](limit_server_subscription_queue_size.html)**
-
-- **[Tune the Client's Subscription Message Tracking Timeout](tune_client_message_tracking_timeout.html)**
-
-
