diff --git a/css/glowingbear.css b/css/glowingbear.css
index 44364a9..d585367 100644
--- a/css/glowingbear.css
+++ b/css/glowingbear.css
@@ -269,7 +269,6 @@ input[type=text], input[type=password], #sendMessage {
 .nav-pills > li > a {
     border-radius: 0;
     color: #ddd;
-    padding: 5px 10px;
 }
 .nav-pills > li > a:hover, .nav-pills > li > a:hover span {
     color: #222;
diff --git a/index.html b/index.html
index 667583a..aedc9a2 100644
--- a/index.html
+++ b/index.html
@@ -100,7 +100,7 @@
                   <div class="checkbox">
                     <label class="control-label" for="savepassword">
                         <input type="checkbox" id="savepassword" ng-model="settings.savepassword">
-                        Save password in your browser
+                        Save password
                     </label>
                   </div>
                   <div class="checkbox" ng-show="settings.savepassword">
@@ -138,8 +138,8 @@
 /relay add weechat {{ settings.port || 9001 }}
 </pre>
               <span class="label label-danger">WeeChat version 0.4.2 or higher is required.</span><br>
-              The communication goes directly between your browser and your WeeChat relay in plain text. Check the instructions below for help on setting up encrypted communication.
-              Connection settings, including your password, are saved locally in your own browser between sessions.
+              The communication goes directly between the app and your WeeChat relay in plain text. Check the instructions below for help on setting up encrypted communication.
+              Connection settings, including your password, are saved locally on your device between sessions.
               <br>
               <h3>Shortcuts</h3>
               Glowing Bear has a few shortcuts:
@@ -170,19 +170,7 @@
           <div id="collapseThree" class="panel-collapse collapse in">
             <div class="panel-body">
               <p>If you check the encryption box, the communication between browser and WeeChat will be encrypted with TLS.</p>
-              <p><strong>Note</strong>: If you are using a self-signed certificate, you have to visit <a href="https://{{ settings.host }}:{{ settings.port }}/weechat">https://{{ settings.host || 'weechathost' }}:{{ settings.port || 'relayport' }}/weechat</a> in your browser first to add a security exception. You can close that tab once you confirmed the certificate, no content will appear. The necessity of this process is a bug in <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=594502">Firefox</a> and other browsers.</p>
-              <p><strong>Setup</strong>: If you want to use an encrypted session you first have to set up the relay to use TLS. You basically have two options: a self-signed certificate is easier to set up, but requires manual security exceptions. Using a certificate that is trusted by your browser requires more setup, but offers greater convenience later on and does not require security exceptions. You can find a guide to set up WeeChat with a free trusted certificate from StartSSL <a href="https://4z2.de/2014/07/06/weechat-trusted-relay">here</a>. Should you wish to use a self-signed certificate instead, execute the following commands in a shell on the same host and as the user running WeeChat:</p>
-<pre>
-$ mkdir -p ~/.weechat/ssl
-$ cd ~/.weechat/ssl
-$ openssl req -nodes -newkey rsa:4096 -keyout relay.pem -x509 -days 365 -out relay.pem -subj "/CN={{settings.host || 'your weechat host'}}/"
-</pre>
-              <p>If WeeChat is already running, you can reload the certificate and private key and set up an encrypted relay on port {{ settings.port || 9001 }} with these WeeChat commands:</p>
-<pre>
-/set relay.network.password yourpassword
-/relay sslcertkey
-/relay add ssl.weechat {{ settings.port || 9001 }}
-</pre>
+              <p><strong>Note</strong>: If you are using a self-signed certificate that is not trusted by your device, you will not be able to connect using the Glowing Bear app. Unfortunately, that is a platform limitation and there is nothing we can do about that. We recommend that you obtain a trusted certificate. One way to do so is described <a onclick="window.open('https://4z2.de/2014/07/06/weechat-trusted-relay', '_system')">here</a>.</p>
             </div>
           </div>
         </div>
@@ -196,7 +184,7 @@ $ openssl req -nodes -newkey rsa:4096 -keyout relay.pem -x509 -days 365 -out rel
           </div>
           <div id="collapseFive" class="panel-collapse collapse in">
             <div class="panel-body">
-              <p>Glowing bear is built by a small group of developers in their free time. As we're always trying to improve it, we would love getting your feedback and help. If that sounds like something you might enjoy, check out our <a href="https://github.com/glowing-bear/glowing-bear">project page</a> on GitHub!</p>
+              <p>Glowing bear is built by a small group of developers in their free time. As we're always trying to improve it, we would love getting your feedback and help. If that sounds like something you might enjoy, check out our <a href="https://github.com/glowing-bear/glowing-bear">main project page</a> and its <a href="https://github.com/glowing-bear/glowing-bear-cordova">mobile app spin-off</a> on GitHub!</p>
               <p>If you're interested in contributing or simply want to say hello, head over to <strong>#glowing-bear</strong> on <strong>freenode!</strong> We won't bite, promise (-ish).</p>
             </div>
           </div>
@@ -299,7 +287,7 @@ $ openssl req -nodes -newkey rsa:4096 -keyout relay.pem -x509 -days 365 -out rel
           <div class="modal-header">
             <button type="button" class="close" ng-click="closeModal($event)" aria-hidden="true">&times;</button>
             <h4 class="modal-title">Settings</h4>
-            <p>Settings will be stored in your browser.</p>
+            <p>Settings will be stored on your device.</p>
           </div>
           <div class="modal-body">
             <ul class="">