diff --git a/articles/telegram.html b/articles/telegram.html
index baa88c2..0ea2251 100644
--- a/articles/telegram.html
+++ b/articles/telegram.html
@@ -4,6 +4,7 @@
 	<head>
 		<meta http-equiv="Content-type" content="application/xhtml+xml;charset=utf-8"/>
 		<meta name="viewport" content="width=device-width,initial-scale=1"/>
+		<meta http-equiv="onion-location" content="http://spywaredrcdg5krvjnukp3vbdwiqcv3zwbrcg6qh27kiwecm4qyfphid.onion/articles/telegram.html"/>
 		<link rel="icon" href = "../images/favicon.ico"/>
 		<title>Telegram - Spyware Watchdog</title>
 		<link href="../style.css" rel="stylesheet" type="text/css" media="all"/>
@@ -27,7 +28,7 @@
 				<h3>Telegram does not follow its GPLv2 Obligations</h3>
 				<p>Telegram clients are advertised as free software, but in practice the source code is not immediately accessible.<sup><a href="#two">[2]</a></sup>, the delay sometimes being up to 5 months. So, unknown spyware features could be in the official Telegram client binaries that you download, without you knowing. It's recommended that you build an outdated version of telegram from its source code, since it's not provable whether or not the binaries that are distributed have unknown spyware or not.</p>
 			</div>
-  		<hr></hr>
+  			<hr></hr>
 			<div class="center">
 				<h2>Sources</h2>
 				<p><a id="one">1.</a><a href="https://telegram.org/privacy">Telegram Privacy Policy</a> <a href="https://web.archive.org/web/20201012074908/https://telegram.org/privacy">[web.archive.org]</a></p>
