readme polish

Readme.md

@@ -6,7 +6,7 @@ apps on Heroku.
 If `requirements.txt` is present, the PLP considers the directory a Python app
 with packages to install via pip.
 
-Furthermore, if `${project}/settings.py` is present, the PLP considers the
+Furthermore, if `${PROJECT}/settings.py` is present, the PLP considers the
 directory a Python/Django app, and patches `settings.py` to parse the Heroku
 DATABASE_URL config vars. It then sets default process types to use the Django
 web server and console.
@@ -17,17 +17,17 @@ The PLP uses a Makefile for user-controlled hooks into slug compilation. If
 present, the `make environment` rule will be eval'd in the compile script, allowing
 user-defined exports.
 
-A sample Makefile to force a re-build of every pip package is:
+A sample Makefile
+(<a href="https://github.com/heroku/language-pack-python/raw/master/test/canary_django/Makefile">raw</a>)
+to force a re-build of every pip package is:
 
     environment:
     	export PIP_OPTS=--upgrade
 
-(<a href="https://github.com/heroku/language-pack-python/raw/master/test/canary_django/Makefile">raw file</a>)
-
 Django settings.py
 ------------------
-The PLP injects code into settings.py to alias every Heroku database URL
-config var. Every variable of the format ${NAME}_URL => postgres:// will be
+The PLP injects code into `settings.py` to alias every Heroku database URL
+config var. Every variable of the format `${NAME}_URL => postgres://` will be
 added to the settings.DATABASES hash.
 
 On an app with both a shared SHARED_DATABASE_URL and a dedicated
@@ -41,4 +41,4 @@ like:
       'default':                {'ENGINE': 'psycopg2', 'NAME': 'dedicated', ...},
     }
 
-These aliases can be referenced and further modified at the end of the settings file.
+These aliases can be referenced and further modified at the bottom of `settings.py`.