diff --git a/anonymousremoteserver/index.md b/anonymousremoteserver/index.md
index 0d4669f..4fcc3d4 100644
--- a/anonymousremoteserver/index.md
+++ b/anonymousremoteserver/index.md
@@ -6,10 +6,12 @@ xmr: 8AUYjhQeG3D5aodJDtqG499N5jXXM71gYKD8LgSsFB9BUV1o7muLv3DXHoydRTK4SZaaUBq4EAU
 tags:
   - Core Tutorial
 ---
-# Acquiring remote servers anonymously (non-KYC providers) 
+# Renting Remote VPS Servers Anonymously (non-KYC cloud resellers)
 
 ![](../hiddenservice/1.png)
 
+In this tutorial we're going to cover how you can rent remote servers while maintaining your anonymity from the initial payment to the actual use of the server.
+
 ![](../context/anon_remote.png)
 
 ## **Finding out a non-KYC Cloud Provider and Email Provider**
diff --git a/vpsvpnrouting/image-1.png b/vpsvpnrouting/image-1.png
new file mode 100644
index 0000000..a4c65e3
Binary files /dev/null and b/vpsvpnrouting/image-1.png differ
diff --git a/vpsvpnrouting/image-2.png b/vpsvpnrouting/image-2.png
new file mode 100644
index 0000000..4155368
Binary files /dev/null and b/vpsvpnrouting/image-2.png differ
diff --git a/vpsvpnrouting/image-3.png b/vpsvpnrouting/image-3.png
new file mode 100644
index 0000000..41463f4
Binary files /dev/null and b/vpsvpnrouting/image-3.png differ
diff --git a/vpsvpnrouting/image.png b/vpsvpnrouting/image.png
new file mode 100644
index 0000000..5abc8d5
Binary files /dev/null and b/vpsvpnrouting/image.png differ
diff --git a/vpsvpnrouting/index.md b/vpsvpnrouting/index.md
index d2e3e82..5f83b41 100644
--- a/vpsvpnrouting/index.md
+++ b/vpsvpnrouting/index.md
@@ -7,6 +7,31 @@ xmr: 8AUYjhQeG3D5aodJDtqG499N5jXXM71gYKD8LgSsFB9BUV1o7muLv3DXHoydRTK4SZaaUBq4EAU
 
 # Using a VPS to route the traffic to a Self-hosted service (hiding your home public IP from the users) 
 
+## Why is this setup important ?
+
+Suppose you have a server at home and you have a nginx service on it:
+
+![alt text](image-2.png)
+
+If you intend that local webserver to be a public clearnet service, normally you'd need to port-forward it via your home router to be able to allow remote users to reach it.
+
+
+## What do we need for this setup ?
+
+You're going to need the following:
+- [a home server with a local webserver running](../hypervisor_selfhosted/index.md)
+- [A remote server (VPS)](../anonymousremoteserver/index.md)
+- [a clearnet domain](../anondomain/index.md)
+
+We recommend using [Monero](../monerowallet/index.md) to pay for your remote servers and domains, to support the [Monero Circular Economy](../monerofirst/index.md) as much as possible.
+
+## Targeted Setup
+
+The setup we are targeting is the following:
+
+![alt text](image-3.png)
+
+We're going to connect the homeserver to the remote VPS via OpenVPN, and we're going to make it so that the remote VPS's nginx is configured to make sure that we can reach our local nginx webserver with it. 
 
 ## Serverside Remote Setup : Openvpn server 
 
@@ -327,6 +352,9 @@ user@privatevm_clientside:~% curl http://test.yourdoma.in:80
 welcome to the privatevm web server!
 
 ```
+
+![alt text](image-1.png)
+
 And that's it! Now to highlight why this setup is important, as an end user, when i try to see what the public IP of the service is, i can only see that it is this remote server:
 
 ```sh