update information about patches and what to do with them

ContributionReviews.wiki

diff --git a/ContributionReviews.wiki b/ContributionReviews.wiki
index 900819b..4ebb8e6 100644
--- a/ContributionReviews.wiki
+++ b/ContributionReviews.wiki
@@ -70,16 +70,10 @@
 === Patches ===
 
 The term "patches" is used to refer to relatively small changes to the
-code (and, yes, this definition is intentionally vague).  These can either
-be in the form of actual output from the `diff` command, or they can be
-the contents of the commit log message sent to the
-[MailingListsGuidelines#Developer_list developer mailing list] when a
-[ContributionReviews#Committers committer] commits a change using `hg`.
+code (and, yes, this definition is intentionally vague). Usually these are in the form of output from the `diff` command. It is easy to think of patches as changesets (commits), that are not part of repository history yet and can be passed around.
 
-Patches should be presented for review either in the "unified `diff`" format,
-which is the output resulting from the `hg diff` command for Mercurial (the same format
-as that produced by `diff -uNr`), in "git patch" format, which is generated by `git diff` if using git, or in `hg patch` format.
-using Mercurial:
+Patches should be sent for review to the [MailingListsGuidelines#Developer_list developer mailing list] and presented in the "unified `diff`" format, which is de-facto standard  for many tools and the output from the `hg diff` command for Mercurial (the same format as that produced by `diff -uNr`).
+Using Mercurial:
 
 {{{
 cd ~/code/melange