code review edit

Fixes
#247 (comment),
#247 (comment),
#247 (comment)

README.md

@@ -14,7 +14,7 @@ content from the WordPress and Django back-ends through Elasticsearch.
 
 **This project is a work in progress.**
 Nothing presented in this repo—whether in the source code, issue tracker,
-or wiki—is a final product unless it is marked as such or appears on www.consumerfinance.gov.
+or wiki—is a final product unless it is marked as such or appears on consumerfinance.gov.
 
 ![Screenshot of cfgov-refresh](https://cloud.githubusercontent.com/assets/235397/5940816/3529246a-a6db-11e4-9bfc-76d5b5220a36.png)
 
@@ -32,7 +32,7 @@ or wiki—is a final product unless it is marked as such or appears on www.consu
 #### 1. Back-end setup
 
 Follow the [Sheer installation instructions](https://github.com/cfpb/sheer#installation)
-to get sheer installed.
+to get Sheer installed.
 **NOTE:** We suggest creating a virtualenv variable specific to this project,
 such as `cfgov-refresh` instead of `sheer` used in the Sheer installation instructions:
 
@@ -139,6 +139,9 @@ with the proper path to its configuration file. For example, it may look like:
 $ elasticsearch --config=/Users/<YOUR MAC OSX USERNAME>/homebrew/opt/elasticsearch/config/elasticsearch.yml
 ```
 
+> You can add the following to your `.bash_profile` that will allow launching of Elasticsearch with the `elsup` command:
+`alias elsup="elasticsearch --config=/Users/[MAC OSX USERNAME]/homebrew/opt/elasticsearch/config/elasticsearch.yml".
+
 ### 3. Launch Sheer to serve the site
 
 To work on the app you will need Sheer running to compile the templates.
@@ -181,11 +184,11 @@ To run browser tests, you'll need to perform the following steps:
   - Mac: `brew install chromedriver`
   - Manual (Linux/Mac): Download the latest
     [Chromedriver](http://chromedriver.storage.googleapis.com/index.html)
-    binary and put it somehwere on your path (e.g. /path/to/your/venv/bin)
-2. In _tests/browser_testing/features/, copy example-environment.cfg to
-environment.cfg and change the `chrome_driver` path to the proper path
+    binary and put it somehwere on your path (e.g. `/path/to/your/venv/bin`)
+2. In `_tests/browser_testing/features/`, copy `example-environment.cfg` to
+`environment.cfg` and change the `chrome_driver` path to the proper path
 for your webdriver binary.  If you installed via homebrew,
-this will be /path/to/homebrew/bin/chromedriver.
+this will be `/path/to/homebrew/bin/chromedriver`.
 3. `pip install -r _tests/browser_testing/requirements.txt`
 4. `cd _tests/browser_testing/`
 5. Start the tests: `behave`