Cleanup testing

Signed-off-by: Jared Ledvina <jared@techsmix.net>

docs/testing.md

@@ -19,7 +19,7 @@ tests to more quickly iterate on new features.
 1. Fork the [sensu-ansible](https://github.com/sensu/sensu-ansible) repository
 2. `git clone` your fork of the `sensu-ansible` repository and `cd` into your local clone.
 3. Add the `upstream` repo to your local clone of the repository with the following `git` command:
-```
+```bash
 git remote add upstream https://github.com/sensu/sensu-ansible.git
 ```
 4. Execute `git checkout -b feature/NEW_FEATURE_NAME_HERE` to work on a dedicated branch
@@ -28,7 +28,7 @@ git remote add upstream https://github.com/sensu/sensu-ansible.git
 7. Install this repositories development dependacies with `pipenv install --two --dev` followed by ` gem install rubocop`
 8. Execute the full integration tests for your chosen operating system distribution: ` pipenv run molecule test --scenario-name $OS --driver-name docker --destroy always`
 
-Notes:
-1. Currently, you can set `$OS` above to one of `debian`, `ubuntu`, `centos`, `fedora`, or `amazonlinux`
+##### Notes:
+1. Currently, you can set `$OS` above to one of `debian`, `ubuntu`, `centos`, `fedora`, `amazonlinux`, or `oraclelinux`.
 2. It's faster to iterate by changing `--destroy always` to `--destroy never` such that you don't have to full rebuild the testing infrastructure.
-3. If you want to limit testing to just the Inspec unit tests, you can simply run ` pipenv run molecule verify --scenario-name $OS` to re-run those steps.
+3. If you want to limit testing to just the Inspec unit tests, you can simply run `pipenv run molecule verify --scenario-name $OS` to re-run those steps.