From fdc93725dc2aab5e55996f4f6a00241c3f8f7b0b Mon Sep 17 00:00:00 2001
From: Barry O'Donovan <barry@opensolutions.ie>
Date: Sat, 21 Sep 2024 11:35:51 +0000
Subject: [PATCH] Deployed 38c291d0 to 7.0 with MkDocs 1.6.1 and mike 2.1.3

---
 7.0/features/peering-manager/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/7.0/features/peering-manager/index.html b/7.0/features/peering-manager/index.html
index 236428cc..93589566 100644
--- a/7.0/features/peering-manager/index.html
+++ b/7.0/features/peering-manager/index.html
@@ -2254,7 +2254,7 @@ <h1 id="peering-manager">Peering Manager<a class="headerlink" href="#peering-man
 <li><strong>Peers:</strong> Fellow IXP members that you peer with via the route servers, bilaterally or both;</li>
 <li><strong>Rejected / Ignored:</strong> You can move members from any of the other tabs to this tab if you wish to ignore them, or if they have refused peering. This allows you to keep the other lists clean.</li>
 </ul>
-<p>The mechanism for detecting bilateral peers is by by observing established TCP sessions between member peering IP addresses on port 179 using <a href="../grapher/sflow.md]">sflow</a>. See the <a href="../peering-matrix/">peering matrix documentation</a> as setting up the peering matrix will provide all the data needed for the peering manager.</p>
+<p>The mechanism for detecting bilateral peers is by by observing established TCP sessions between member peering IP addresses on port 179 using <a href="sflow.md]">sflow</a>. See the <a href="../peering-matrix/">peering matrix documentation</a> as setting up the peering matrix will provide all the data needed for the peering manager.</p>
 <p><strong>NB: You must check the <em>Peering Manager</em> option when editing VLANs for that VLAN to be included in the peering manager.</strong></p>
 <p>The features of the peering manager include:</p>
 <ul>