diff --git a/opsec/onionbalancelb/1.0.png b/opsec/onionbalancelb/1.0.png
new file mode 100644
index 0000000..a798528
Binary files /dev/null and b/opsec/onionbalancelb/1.0.png differ
diff --git a/opsec/onionbalancelb/1.png b/opsec/onionbalancelb/1.1.png
similarity index 100%
rename from opsec/onionbalancelb/1.png
rename to opsec/onionbalancelb/1.1.png
diff --git a/opsec/onionbalancelb/index.html b/opsec/onionbalancelb/index.html
index 610b85d..b06df49 100644
--- a/opsec/onionbalancelb/index.html
+++ b/opsec/onionbalancelb/index.html
@@ -101,15 +101,24 @@ When one backend instance becomes unavailable, users will still be able to acces
 </p>
 
 <p>
-At the end of this guide, we'll have a load-balanced frontend URL available to users. Here's a diagram illustrating the desired result:
+At the end of this guide, we'll have a load-balanced frontend URL. There is simplified diagram of how this works:
 </p>
 
-<img src="1.png" class="imgRz">
+<img src="1.0.png" class="imgRz">
 
 <br><br>
 
 <p>
-From an end user's perspective accessing our store:
+User accessing the frontend gets transparently redirected to either of the backends.<br><br>
+A more detailed version presenting how clients get connected to the load-balanced service over Tor:
+</p>
+
+<img src="1.1.png" class="imgRz">
+
+<br><br>
+
+<p>
+From an end user's perspective:
 <ul>
     <li><b>1</b> - Tor client makes a request to the Distributed Hash Table (DHT) with the address of vegetable shop.</li><br>
     <li><b>2</b> - The DHT returns a descriptor with multiple backend addresses. Tor client chooses one of the addresses.</li><br>