X-Git-Url: https://gitweb.stoutner.com/?a=blobdiff_plain;f=app%2Fsrc%2Fmain%2Fassets%2Fen%2Fguide_ssl_certificates_dark.html;h=52dfccd516415fe8bca1725f054c07a271e12457;hb=dab795a417200c6094da1b1aa25c7bb3e638c686;hp=d24d78c6e2af4d68cd61ad3af86688c59ec11959;hpb=012e5595c82d6e8d0b8a46f1ef18a02a56341182;p=PrivacyBrowserAndroid.git

diff --git a/app/src/main/assets/en/guide_ssl_certificates_dark.html b/app/src/main/assets/en/guide_ssl_certificates_dark.html
index d24d78c6..52dfccd5 100644
--- a/app/src/main/assets/en/guide_ssl_certificates_dark.html
+++ b/app/src/main/assets/en/guide_ssl_certificates_dark.html
@@ -1,5 +1,5 @@
 <!--
-  Copyright © 2017-2018 Soren Stoutner <soren@stoutner.com>.
+  Copyright © 2017-2019 Soren Stoutner <soren@stoutner.com>.
 
   This file is part of Privacy Browser <https://www.stoutner.com/privacy-browser>.
 
@@ -28,22 +28,26 @@
 
         <p>When visiting an encrypted URL (one that begins with HTTPS), the webserver uses an SSL certificate to both encrypt the information sent to the browser and to identify the server.
             The purpose of the server identification is to prevent a machine located between the browser and the webserver from pretending to be the server and decrypting the information in transit.
-            This type of attack is known as a Man In The Middle (MITM) attack. SSL certificates are generated by certificate authorities: companies that verify a server’s identity and produce a certificate for a fee.
+            This type of attack is known as a Man In The Middle (MITM) attack.
+            SSL certificates are generated by certificate authorities: companies that verify a server’s identity and produce a certificate for a fee.
             Android has a list of trusted certificate authorities, and will accept any of their certificates for any website.
-            It isn’t supposed to be possible for an organization to acquire an SSL certificate for a domain they do not control, but in practice many governments and large corporations have been able to do so.</p>
+            It isn’t supposed to be possible for an organization to acquire an SSL certificate for a domain they do not control,
+            but in practice many governments and large corporations have been able to do so.</p>
 
         <p>Pinning an SSL certificate tells the browser that only one specific SSL certificate is to be trusted for a particular domain. Any other certificate, even if it is valid, will be rejected.</p>
 
-        <p><img class="center" src="images/ssl_certificate_mismatch.png"></p>
+        <p><img class="center" src="images/pinned_mismatch.png"></p>
 
         <p>SSL certificates expire on a specified date, so even pinned SSL certificates will legitimately need to be updated from time to time.
             As a general rule, pinning SSL certificates probably isn’t needed in the majority of cases.
-            But for those who suspect that powerful organizations may be targeting them, SSL certificate pinning can detect and thwart a MITM attack.</p>
+            But for those who suspect that powerful organizations may be targeting them, SSL certificate pinning can detect and thwart a MITM attack.
+            Privacy Browser also has the ability to pin IP addresses.</p>
 
         <p><img class="center" src="images/pinned_ssl_certificate.png"></p>
 
         <p>SSL certificates can be pinned in Domain Settings.
-            Besides protecting against MITM attacks, pinning a self-signed certificate for a device like a wireless router or access point will remove the error message that is normally presented every time its website is loaded.
-            To view the current website SSL certificate, tap on the favorite icon next to the URL bar.</p>
+            Besides protecting against MITM attacks,
+            pinning a self-signed certificate for a device like a wireless router or access point will remove the error message that is normally presented every time its website is loaded.
+            Tapping on the active tab displays the current website SSL certificate.</p>
     </body>
 </html>
\ No newline at end of file