Documentation improvements.

Author: michaelsanford

docs/installing.markdown

@@ -14,11 +14,15 @@ order: 1
 
 On first launch, `Bittray` will ask for two things:
 
-1. The URL of your Bitbucket Enterprise server, and
-1. The username you use to log in to Bitbucket
+1. The username you use to log in to Bitbucket, and
+1. The URL of your Bitbucket server
 
-These two settings are stored in the [Windows Credential Manager](https://support.microsoft.com/en-ca/help/4026814/windows-accessing-credential-manager)
- as a _Windows Credential_ under the key `bittray:conf`.
+    These two settings are stored in the [Windows Credential Manager](https://support.microsoft.com/en-ca/help/4026814/windows-accessing-credential-manager)
+    as a _Windows Credential_ under the key `bittray:conf`.
+
+ 1. You will then be asked for your Bitbucket password.
+ 
+     It will be not stored and is only valid until you quit Bittray. See [Security]({{ site.baseurl }}/security) for more details.
 
 ### Note
 The  URL must take _exactly_ the format `http://example.com:7990`, with a port (if not `80`) and no trailing slash.

docs/security.md

@@ -15,13 +15,13 @@ You will be asked to provide the password you use to log in to Bitbucket _every
 
 The WCM [is not a secure password store](https://github.com/michaelsanford/bittray/issues/14) by default.
 
-In order to securely store the password in the WCM in a retrievable form, I would have needed to encrypt it using
+In order to securely store the password in the WCM (or registry, or anywhere) in a retrievable form, it would need to be encrypted using
 a passphrase provided by the user.
 
 The user would need to enter that decryption passphrase every time `Bittray` launched to decrypt the stored Bitbucket
 credentials.
 
-It saves no clicks to store it.
+It saves no effort to store it.
 
 Storing it is arguably actively harmful.
 

docs/using.md

@@ -7,14 +7,14 @@ order: 2
 
 # What Counts as "Pending"
 
-A Pull Request will appear in the pending queue and provoke the alarm icon if
+A Pull Request will appear in the Pending queue and provoke the alarm icon if
 
-1. You are involved as a Reviewer
+1. You are involved as a Reviewer, and
 1. You have not clicked `Approved` or `Needs Work`
 
-Clicking `Needs Work` signifies to the developer that the PR requires attention, and it will remove it from your queue.
+Clicking `Needs Work` says to the developer that the PR requires attention and will remove it from your queue because you've "done something about it".
 
-The next time the developer pushes, the `Needs Work` flag is automatically cleared and the request will fall back into Pending.
+When the developer pushes a new changeset, the `Needs Work` flag is automatically cleared and the request will fall back into Pending.
 
 # Icon States