Docs changes

- a constant state of disaster

CONTRIBUTING.md

@@ -18,13 +18,15 @@ the issues page.
 
 If you decide to take on an issue for Go you will need to work in a branch off
 of the current development branch (ie. `2.3-dev` with 2.3 being the version in
-    development).
+development).
 
 This can be done with the following chain of `git` commands within `go/`:
 
-    git pull
-    git checkout 2.3-dev
-    git checkout -B ##-shortdescription
+```sh
+git pull
+git checkout 2.3-dev
+git checkout -B ##-shortdescription
+```
 
 **Note:**
 
@@ -34,9 +36,11 @@ does.
 
 **Example:**
 
-    git pull
-    git checkout 2.3-dev
-    git checkout -B 102-readmeUpdates
+```sh
+git pull
+git checkout 2.3-dev
+git checkout -B 102-readmeUpdates
+```
 
 If you are working on something that does not have an issue please open a new
 issue before creating your branch.

README.md

@@ -221,6 +221,18 @@ repository and is named go-cleanlinks.cron. Drop this in cron.hourly and
 change the paths so that they point to the virtualenv activate script and
 manage.py.
 
+## Production cron job
+
+```sh
+#!/bin/bash
+# Cron job to automatically expire outdated links, put this in cron.hourly
+ACTIVATE_PATH=/path/to/virtualenv/activate
+MANAGE_PATH=/path/to/go/manage.py
+
+source ${ACTIVATE_PATH}
+python ${MANAGE_PATH} expirelinks
+```
+
 ---
 **Note:**
 

go-cleanlinks.cron

-#!/bin/bash
-# Cron job to automatically expire outdated links, put this in cron.hourly
-ACTIVATE_PATH=/path/to/virtualenv/activate
-MANAGE_PATH=/path/to/go/manage.py
-
-source ${ACTIVATE_PATH}
-python ${MANAGE_PATH} expirelinks