fixes #416
Fix duplicate import statements
move requirements to folder so they can be picked up by a requirements analysis tool
Actually answer "why" on the "journalist public key" page. Also note that signing will at least let us know what keyid was used, so users needing anonymity probably shouldn't.
Update "you can encrypt with our public key" bottom msg.

The only people who should really do that are users already familiar w/PGP (as noted in the "why encrypt with key" page that we link to here). So let's make that explicit right off the bat so we don't scare people. Also mention that submissions become encrypted upon receipt.
Describe "logging back in" so users know what to expect, know why they should come back.

1) we should make sure the user knows the codename is important (and why!)
2) give them guidance that they should come back later once they have submitted

I feel like this might be a bit too wordy, but I think this sets the expectations much better for a non-techy submitter.

Re: #479
Add pip-tools to test dependencies
Add pip_update.sh
Updated pip packages with pip-review
make codname length dropdown ("7 words", "8 words"...) more consistent. #494
Fix grammar.
Need sudo to run add-journalists.sh and add-admin.sh.
store shared strings in variables based on feedback from @diracdeltas; fix failing tests. re: #479 #489
be more explicit about when securedrop receive-end encryption happens. (after it's submitted/when it's received, rather than "when it is submitted"). #488
Updated the guide for the 0.3 release
Include changes from @dolanjs
Merge pull request #484 from Bachmann1234/highlight-requirements

Consolidate requirements so they can be analyzed
Merge pull request #488 from mtigas/copy-edits-a

Explain "optionally GPG encrypt w/public key" better
fix broken functional tests
prefer .format to % (nit)