From 8582c13ed5878e316f5cb289a75b0a6ecd289f8e Mon Sep 17 00:00:00 2001
From: Chris Cho <chris.cho@mongodb.com>
Date: Wed, 16 Aug 2023 18:03:47 -0400
Subject: [PATCH] Fix link to renamed and reformatted spec (#122)

(cherry picked from commit 49ad33b1cc0a3a176058e4198dfe99a52474c253)
---
 source/fundamentals/monitoring.txt | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/source/fundamentals/monitoring.txt b/source/fundamentals/monitoring.txt
index be4637ac..a32bb48e 100644
--- a/source/fundamentals/monitoring.txt
+++ b/source/fundamentals/monitoring.txt
@@ -148,8 +148,7 @@ The driver defines nine SDAM events. The driver divides these nine events
 between three separate listener interfaces which each listen for three of the
 nine events. Here are the three interfaces and the events they listen for:
 
-- ``ClusterListener``: :spec:`topology </server-discovery-and-monitoring/server-discovery-and-monitoring.rst#topology>`
-  related events
+- ``ClusterListener``: topology-related events
 - ``ServerListener``: events related to ``mongod`` or ``mongos`` processes
 - ``ServerMonitorListener``: heartbeat related events
 
@@ -157,8 +156,7 @@ To monitor a type of SDAM event, write a class that
 implements one of the three preceding interfaces and register an instance of that
 class with your ``MongoClient`` instance.
 
-For a detailed description of each SDAM event in the driver, see the
-:spec:`MongoDB SDAM monitoring specification </server-discovery-and-monitoring/server-discovery-and-monitoring-monitoring.rst#events>`.
+For a detailed description of each SDAM event, see the :spec:`MongoDB SDAM monitoring events specification </server-discovery-and-monitoring/server-discovery-and-monitoring-logging-and-monitoring.rst#events-api>`.
 
 Example
 ^^^^^^^