X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=contributing.mdwn;h=7c5323a24c3997c0cc44834c40ecfb6f68317aea;hb=6af7f7dbf56bba07b8e3dcd567f51230c230b8d4;hp=c92853fd90b9108d97c033edcf07217eae4d7bbf;hpb=841fd6493f9fede3e3ea6fefabfe5e80a4b1b77f;p=notmuch-wiki

diff --git a/contributing.mdwn b/contributing.mdwn
index c92853f..7c5323a 100644
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -59,7 +59,7 @@ Each commit should contain one logical change only. The code should
 build and the tests should pass after each commit. Changes to lib,
 cli, emacs, tests, man pages, or news are usually best kept
 separate. Also separate cleanups from functional changes. See the
-Notmuch source history (**`git log`**) for examples.
+Notmuch source history (`git log`) for examples.
 
 For in-depth discussion on the subject, see
 [Software Release Practice HOWTO](http://tldp.org/HOWTO/Software-Release-Practice-HOWTO/) by Eric S. Raymond.
@@ -75,8 +75,8 @@ See also
 on commit guidelines, including commit messages.
 
 It is customary to prefix the subject line with "lib:", "cli:", "emacs:",
-etc. depending on which part of Notmuch the commit is changing. See
-**`git log`** for examples.
+etc. depending on which part of Notmuch the commit is changing. See `git log`
+for examples.
 
 Wrap the lines to about 72 characters.
 
@@ -134,7 +134,7 @@ before submitting patches.
 ## Send your patches to the mailing list
 
 Changes to Notmuch are contributed as [emailed
-patches](http://git-scm.com/book/en/Distributed-Git-Contributing-to-a-Project#Public-Large-Project).
+patches](http://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#Public-Project-over-Email).
 Once you have your changes ready in your local repository, you need to
 send them to the Notmuch mailing list. The simplest way is to use `git
 send-email` to send the patches directly from your repository: