X-Git-Url: https://git.cworth.org/git?a=blobdiff_plain;f=contributing.mdwn;h=c92853fd90b9108d97c033edcf07217eae4d7bbf;hb=c497ef55c81aac592539e672c630d413de08ebf1;hp=8650e1311f8338d804fcbce47d9e1a3f539ee7bb;hpb=e3355ef27b3593f76acf98d9d4ce8602dd7578ee;p=notmuch-wiki

diff --git a/contributing.mdwn b/contributing.mdwn
index 8650e13..c92853f 100644
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -9,7 +9,8 @@ but once you get the hang of it, it'll be fun. This page should help
 you get there. DON'T PANIC.
 
 The headlines below act as a checklist. Not all of them apply in all
-situations; use common sense.
+situations. Use your best judgment, and the Notmuch community will
+help out as needed.
 
 [[!toc levels=2]]
 
@@ -105,7 +106,7 @@ in the Notmuch source for further information.
 ## Update the documentation
 
 If you modify or add new features to the Notmuch command-line tools,
-you should update the manual pages under the `man` directory of the
+you should update the manual pages under the `doc` directory of the
 Notmuch source.
 
 If you modify or add new features to the Notmuch Emacs UI, you should
@@ -168,7 +169,7 @@ like email. This applies to patch and bug tracking as well. The
 Notmuch project uses [nmbug](http://notmuchmail.org/nmbug/) for
 tracking. The Notmuch developers will tag your patches too, making
 them show up in the
-[nmbug status page](http://nmbug.tethera.net/status/), but requesting
+[nmbug status page](http://nmbug.notmuchmail.org/status/), but requesting
 access and tagging your patches yourself will be helpful in the long
 run.