diff --git a/book/02-git-basics/sections/remotes.asc b/book/02-git-basics/sections/remotes.asc
index a150fbf6b..7332afce8 100644
--- a/book/02-git-basics/sections/remotes.asc
+++ b/book/02-git-basics/sections/remotes.asc
@@ -11,8 +11,8 @@ In this section, we'll cover some of these remote-management skills.
 [NOTE]
 .Remote repositories can be on your local machine.
 ====
-It is entirely possible that you can be working with a ``remote'' repository that is, in fact, on the same host you are.
-The word ``remote'' does not necessarily imply that the repository is somewhere else on the network or Internet, only that it is elsewhere.
+It is entirely possible that you can be working with a `remote` repository that is, in fact, on the same host you are.
+The word "remote" does not necessarily imply that the repository is somewhere else on the network or Internet, only that it is elsewhere.
 Working with such a remote repository would still involve all the standard pushing, pulling and fetching operations as with any other remote.
 ====
 
@@ -118,7 +118,7 @@ $ git fetch <remote>
 The command goes out to that remote project and pulls down all the data from that remote project that you don't have yet.
 After you do this, you should have references to all the branches from that remote, which you can merge in or inspect at any time.
 
-If you clone a repository, the command automatically adds that remote repository under the name ``origin''.
+If you clone a repository, the command automatically adds that remote repository under the name `origin`.
 So, `git fetch origin` fetches any new work that has been pushed to that server since you cloned (or last fetched from) it.
 It's important to note that the `git fetch` command only downloads the data to your local repository -- it doesn't automatically merge it with any of your work or modify what you're currently working on.
 You have to merge it manually into your work when you're ready.