diff --git a/opsec/anonymous_server_monitoring/index.html b/opsec/anonymous_server_monitoring/index.html
index 1106f5b..d805e0e 100644
--- a/opsec/anonymous_server_monitoring/index.html
+++ b/opsec/anonymous_server_monitoring/index.html
@@ -165,7 +165,7 @@
                 In the following part of the post we will look into:
 
                 <ul>
-                    <li>How to connect to your server safely and anonymously</li>
+                    <li>How to connect to your server safely and anonymously (see <a href="http://blog.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/opsec/anonymousremoteserver/index.html">this article</a>) </li>
                     <li>How to set up advanced monitoring tools so you don't have to keep an eye on a bunch of tmux sessions with glances/top open</li>
                 </ul>
           
@@ -180,28 +180,16 @@
 	    <div class="container">
 			<div class="row">
 				<div class="col-lg-8 col-lg-offset-2">
-                    <h1><b>Power tools</b></h1>
+          
+	       </div>
+			</div><!-- /row -->
+	    </div> <!-- /container -->
+	</div><!-- /grey -->
 
-                    Before getting started let's review our tools and reminds ourselves of the security implications of their use:
-
-                    <ul>
-                        <li>Tor: if you're reading this, you already know what it is.<br>
-                            <b>Risks:</b>
-                            <ul>
-                                <li> Information leakage: if you try to resolve "mysecretillegalhostingserver.onion" against your ISP's DNS server it will leave an incriminating log: unless your server is well-known and has a lot of traffic you can't really justify knowing it's onion address </li>
-                            </ul>
-                        </li>
-                        <li> SSH: Secure SHell. This tools allows you to connect to a remote server with an encrypted tunnel, this providing you with confidentiality when doing administration tasks.
-                            <br>
-                            <b>Risks</b>
-                            <ul>
-                                <li>Authentication: the first time you connect to a server you should check its host key fingerprint. This is <b>NOT</b> an issue in our case since tor will provide another couple of layers of authentication. If you connect on a clearweb server through tor though you will want to check the host key fingerprint to make sure your exit node isn't trying to MITM you.</li>
-                                <li>Password security: Nefarious operators trawl through the web on a daily basis trying credential stuffing attacks (logging into your server with weak/well known passwords), if you set up root:toor
-                                    as a login you will get compromised quickly. </li>
-                                <li>Information leakage: instead of setting up a password you decide to do things more securely and use an ssh key as a mean of authentication. By default, the ssh client will <b>try every key it has until succeeding when connecting to a server</b>. Why is that bad? Say your cloud provider decides to log verbosely your VPS' ssh server connection. When you connect next they might get a bunch of public keys that you use on other services. If Leo decides to ask github if anyone is using any of those keys to, say, push code to repositories or deploy stuff through actions then they will have a link between your github account and your onion server. Let's hope you haven't set up a personal email with github, because if you did, you're toast.</li>
-                            </ul>
-                        </li>
-                    </ul>
+	<div id="anon2">
+	    <div class="container">
+			<div class="row">
+				<div class="col-lg-8 col-lg-offset-2">
 
           
 	       </div>
@@ -209,6 +197,7 @@
 	    </div> <!-- /container -->
 	</div><!-- /grey -->
 
+
 	<div id="anon3">
 	    <div class="container">
 			<div class="row">