Make password.txt example consistent

Author: crd

book/07-git-tools/sections/rewriting-history.asc

@@ -273,7 +273,7 @@ This occurs fairly commonly.
 Someone accidentally commits a huge binary file with a thoughtless `git add .`, and you want to remove it everywhere.
 Perhaps you accidentally committed a file that contained a password, and you want to make your project open source.
 `filter-branch` is the tool you probably want to use to scrub your entire history.
-To remove a file named passwords.txt from your entire history, you can use the `--tree-filter` option to `filter-branch`:
+To remove a file named `passwords.txt` from your entire history, you can use the `--tree-filter` option to `filter-branch`:
 
 [source,console]
 ----
@@ -283,7 +283,7 @@ Ref 'refs/heads/master' was rewritten
 ----
 
 The `--tree-filter` option runs the specified command after each checkout of the project and then recommits the results.
-In this case, you remove a file called passwords.txt from every snapshot, whether it exists or not.
+In this case, you remove a file called `passwords.txt` from every snapshot, whether it exists or not.
 If you want to remove all accidentally committed editor backup files, you can run something like `git filter-branch --tree-filter 'rm -f *~' HEAD`.
 
 You’ll be able to watch Git rewriting trees and commits and then move the branch pointer at the end.