formatted code and command names in change history; grammar

diff --git a/Home.textile b/Home.textile
index 274a23b590d4ac5799ee9dcb04be8141605cb7be..11178d8370afddbf85e6b25b4019a3b70fd6c907 100644 (file)
--- a/Home.textile
+++ b/Home.textile
@@ -26,25 +26,25 @@ As Dscho put it, submodules are the "neglected ugly duckling" of git. Time to ch
 *Issues already solved and merged into Junio's Repo:*
 
 * Since git 1.6.6:
-** New --submodule option to "git diff" (many thanks to Dscho for writing the core part!)
-** Display of submodule summaries instead of plain hashes in git gui and gitk
+** New @--submodule@ option to @git diff@ (many thanks to Dscho for writing the core part!)
+** Display of submodule summaries instead of plain hashes in @git gui@ and @gitk@
 * Since git 1.7.0:
-** "git status" and "git diff*" show submodules with untracked or modified files in their work tree as "dirty"
-** git gui: New popup menu for submodule diffs
+** @git status@ and @git diff*@ show submodules with untracked or modified files in their work tree as "dirty"
+** @git gui@: New popup menu for submodule diffs
 * Since git 1.7.1:
 ** Show the reason why working directories of submodules are dirty (untracked content and/or modified content) in superproject
 * Since git 1.7.2:
-** Add parameters to the "--ignore-submodules" option for "git diff" and "git status" to control when a submodule is considered dirty
+** Add parameters to the @--ignore-submodules@ option for @git diff@ and @git status@ to control when a submodule is considered dirty
 * Since git 1.7.3:
-** Add the "ignore" config option for the default behaviour of "git diff" and "git status". Both .git/config and .gitmodules are parsed for this option, the value set in .git/config. will override that from .gitmodules
+** Add the "ignore" config option for the default behaviour of @git diff@ and @git status@. Both .git/config and .gitmodules are parsed for this option; the value set in .git/config. will override that from .gitmodules
 ** Add a global config option to control when a submodule is considered dirty (written by Dscho)
 ** Better support for merging of submodules (thanks to Heiko Voigt for writing that)
 * Since git 1.7.4:
 ** Recursive fetching of submodules can be enabled via command line option or configuration.
 * Since git 1.7.5:
-** fetch runs recursively on submodules by default when new commits have been recorded for them in the superproject
+** @fetch@ runs recursively on submodules by default when new commits have been recorded for them in the superproject
 * Since git 1.7.7:
-** git push learned the --recurse-submodules=check option which errors out when trying to push a superproject commit where the submodule changes are not pushed (part of Frederik Gustafsson's 2011 GSoC project)
+** @git push@ learned the @--recurse-submodules=check@ option, which errors out when trying to push a superproject commit where the submodule changes are not pushed (part of Frederik Gustafsson's 2011 GSoC project)
 * Since git 1.7.8:
-** The "update" option learned the value "none" which disables "submodule init" and "submodule update"
-** The git directory of a newly cloned submodule is stored in the .git directory of the superproject, the submodules work tree contains only a gitfile. This is the first step towards recursive checkout, as it enables us to remove a submodule directory (part of Frederik Gustafsson's 2011 GSoC project)
\ No newline at end of file
+** The @update@ option learned the value @none@, which disables @submodule init@ and @submodule update@
+** The git directory of a newly cloned submodule is stored in the .git directory of the superproject; the submodules work tree contains only a gitfile. This is the first step towards recursive checkout, as it enables us to remove a submodule directory (part of Frederik Gustafsson's 2011 GSoC project)
\ No newline at end of file