From: Jani Nikula <jani@nikula.org>
Date: Sun, 21 Feb 2016 20:27:15 +0000 (+0200)
Subject: Revert "bold `git log`..."
X-Git-Url: https://git.cworth.org/git?a=commitdiff_plain;ds=sidebyside;h=d451f65555201e49f8d34fc357e8ebcbd8effd90;p=notmuch-wiki

Revert "bold `git log`..."

This reverts commit 09362e87f771dd37a5f04854499db0158c0c823c.

There's tons of backticked `commands` over there, no need to make `git
log` stand out from the rest.
---

diff --git a/contributing.mdwn b/contributing.mdwn
index 31109bf..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.