diff --git a/snappass/static/bootstrap/js/npm.js b/snappass/static/bootstrap/js/npm.js
deleted file mode 100644
index bf6aa80..0000000
--- a/snappass/static/bootstrap/js/npm.js
+++ /dev/null
@@ -1,13 +0,0 @@
-// This file is autogenerated via the `commonjs` Grunt task. You can require() this file in a CommonJS environment.
-require('../../js/transition.js')
-require('../../js/alert.js')
-require('../../js/button.js')
-require('../../js/carousel.js')
-require('../../js/collapse.js')
-require('../../js/dropdown.js')
-require('../../js/modal.js')
-require('../../js/tooltip.js')
-require('../../js/popover.js')
-require('../../js/scrollspy.js')
-require('../../js/tab.js')
-require('../../js/affix.js')
\ No newline at end of file
diff --git a/snappass/templates/set_password.html b/snappass/templates/set_password.html
index 5cec98b..ea81af1 100644
--- a/snappass/templates/set_password.html
+++ b/snappass/templates/set_password.html
@@ -27,16 +27,14 @@
       </form>
     </div>
 
-    <h3>How SnapPass Works</h3>
-    <p>SnapPass allows you to share passwords with anybody in a secure, ephemeral way.</p>
+    <h3>Using SnapPass</h3>
+    <p>SnapPass allows you to share passwords in a secure, ephemeral way.</p>
 
-    <p>Input a password and set a time to live. The default is one week.</p>
+    <ol>
+      <li>Input a password, its expiration time, and click Generate URL</li>
+      <li>Share the one-time use URL with your intended recipient</li>
+    </ol>
 
-    <p>Once you click the Generate URL button, a unique URL is generated. That unique URL can only be accessed once.</p>
-
-    <p>Share that URL to whomever is the intended recipient of the password. If the URL is never accessed, the URL and the corresponding password will be deleted per the time to live you set. However, if the URL is accessed by your intended recipient, or perhaps an unintended recipient, the URL and the corresponding password will be deleted at that moment.</p>
-
-    <p>If your intended recipient was able to access the URL and retrieve the password, there is a high probability only they saw the password. However, if your intended recipient encountered a 404 when accessing the URL, there is a high probability the URL expired or an unintended recipient accessed the URL through whatever service (email, chat, text) the URL was sent over.</p>
     </section>
 </div>
 {% endblock %}