From 65a3837ecc66def849bb4ce354a917982278c363 Mon Sep 17 00:00:00 2001
From: midas <midas@mullsec>
Date: Sat, 8 Mar 2025 11:11:37 +0100
Subject: [PATCH] more polishing

---
 opsec/anonymous_server_monitoring/index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/opsec/anonymous_server_monitoring/index.html b/opsec/anonymous_server_monitoring/index.html
index 0db577c..b96ab2c 100644
--- a/opsec/anonymous_server_monitoring/index.html
+++ b/opsec/anonymous_server_monitoring/index.html
@@ -175,7 +175,7 @@
                 <br><br>
 
                 This tutorial will assume that you have acquired servers anonymously via non-KYC cloud providers, and that you are only accessing them anonymously through tor
-                See <a href="../opsec/anonymousremoteserver/index.html">this article</a> if you have not already.
+                See <a href="../anonymousremoteserver/index.html">this article</a> if you have not already.
                 <br>
                 <br>
                 ...
@@ -204,7 +204,7 @@
                         <br>
                         <ul>
                             <li>Our whonix workstation will connect through tor to a central monitoring server in order to access the grafana dashboard containing our monitoring data.</li>
-                            <li>Our monitoring server will itself connecth through tor to the target monitored servers using prometheus</li>
+                            <li>Our monitoring server will itself connect through tor to the target monitored servers using prometheus</li>
                         </ul>
 
                         <h1><b>Setting up the central monitoring server</b></h1>