💄

Author: ben

en/book/10-git-in-other-environments/chapter10.asc

@@ -75,15 +75,7 @@ Each of them is tailored for a specific purpose (viewing history and creating co
 
 ==== GitHub Desktop
 
-[[github_win]]
-.GitHub for Windows.
-image::images/github-win.png[GitHub for Windows.]
-
-[[github_mac]]
-.GitHub for Mac.
-image::images/github-win.png[GitHub for Mac.]
-
-// TODO: wait for Desktop? At least for source-list on Windows.
+**TODO**: wait for Desktop? At least for source-list on Windows.
 
 ==== Other GUIs
 
@@ -97,11 +89,7 @@ Starting with Visual Studio 2013 Update 1, Visual Studio users have a Git client
 Visual Studio has had source-control integration features for quite some time, but they were oriented towards centralized, file-locking systems, and Git was not a good match for this workflow.
 Visual Studio 2013's Git support is a separate feature with its own command pane, but integrates with your day-to-day work just as well as the older feature.
 
-* Commiting
-* diffing
-* history
-* syncing
-* others?
+**TODO**
 
 === Git in Eclipse
 
@@ -174,8 +162,7 @@ cherry            -- find commits not merged upstream
 cherry-pick       -- apply changes introduced by some existing commits
 ----
 
-Ambiguous tab-completions aren't just listed.
-They have helpful descriptions, and you can graphically navigate the list by repeatedly hitting tab.
+Ambiguous tab-completions aren't just listed; they have helpful descriptions, and you can graphically navigate the list by repeatedly hitting tab.
 This works with Git commands, their arguments, and names of things inside the repository (like refs and remotes), as well filenames and all the other things Zsh knows how to tab-complete.
 
 Zsh happens to be fairly compatible with Bash when it comes to prompt customization, but it allows you to have a right-side prompt as well.