SETUP.md: add markdown code blocks to shell commandscolby/setup-doc-formatting

1 files changed, 5 insertions, 5 deletions

diff --git a/doc/development/SETUP.md b/doc/development/SETUP.md
index 10f8dd30f1..2011651252 100644
--- a/doc/development/SETUP.md
+++ b/doc/development/SETUP.md
@@ -4,23 +4,23 @@ Bundler doesn't use a Gemfile to list development dependencies, because when we
 
 1. Install `groff-base` and `graphviz` packages using your package manager, e.g for ubuntu
 
-      $ sudo apt-get install graphviz groff-base -y
+      `$ sudo apt-get install graphviz groff-base -y`
 
    and for OS X (with brew installed)
 
-      $ brew install graphviz homebrew/dupes/groff
+      `$ brew install graphviz homebrew/dupes/groff`
 
 2. Install Bundler's development dependencies
 
-      $ bin/rake spec:deps
+      `$ bin/rake spec:deps`
 
 3. Run the test suite, to make sure things are working
 
-      $ bin/rake spec
+      `$ bin/rake spec`
 
 4. Set up a shell alias to run Bundler from your clone, e.g. a Bash alias:
 
-      $ alias dbundle='BUNDLE_TRAMPOLINE_DISABLE=1 ruby -I /path/to/bundler/lib /path/to/bundler/exe/bundle'
+      `$ alias dbundle='BUNDLE_TRAMPOLINE_DISABLE=1 ruby -I /path/to/bundler/lib /path/to/bundler/exe/bundle'`
 
    The `BUNDLE_TRAMPOLINE_DISABLE` environment variable ensures that the version of Bundler in `/path/to/bundler/lib` will be used. Without that environment setting, Bundler will automatically download, install, and run the version of Bundler listed in `Gemfile.lock`. With that set up, you can test changes you've made to Bundler by running `dbundle`, without interfering with the regular `bundle` command.