Backtick those branches.

rsese · rsese · commit 8ed5b8a6f267 · 2013-03-08T00:56:41.000-08:00
diff --git a/content/guides/getting-started.md b/content/guides/getting-started.md
@@ -383,13 +383,13 @@ can do with the API that you can't do on github.com. Using the API, you can
 turn an issue into a Pull Request.
 
 But at this point, if you want to run this example to convert your issue to a
-pull request, you'll need to create a branch called new-feature with at least
-one commit so it's ahead of the master branch. Otherwise, if we try and convert
-the issue to a pull request now, we'll receive a `422` error telling us that
-there's no commits between master and new-feature.
+pull request, you'll need to create a branch called `new-feature` with at least
+one commit so it's ahead of the `master` branch. Otherwise, if we try and
+convert the issue to a pull request now, we'll receive a `422` error telling us
+that there's no commits between `master` and `new-feature`.
 
-If you've created the new-feature branch and made a commit to it, let's convert
-the issue we created in the previous section:
+If you've created the `new-feature` branch and made a commit to it, let's
+convert the issue we created in the previous section:
 
     curl -i -H 'Authorization: token 5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4' \
          -d '{ \
