Merge branch 'ad/submitting-patches-title-decoration'

Doc update around use of "format-patch --subject-prefix" etc.

* ad/submitting-patches-title-decoration:
  doc/SubmittingPatches: correct subject guidance

diff --cc Documentation/SubmittingPatches
index 17419f7,89f2390..3ef3092
--- 1/Documentation/SubmittingPatches
--- 2/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@@ -203,14 -184,15 +203,15 @@@ lose tabs that way if you are not caref
  
  It is a common convention to prefix your subject line with
  [PATCH].  This lets people easily distinguish patches from other
- e-mail discussions.  Use of additional markers after PATCH and
- the closing bracket to mark the nature of the patch is also
- encouraged.  E.g. [PATCH/RFC] is often used when the patch is
- not ready to be applied but it is for discussion, [PATCH v2],
- [PATCH v3] etc. are often seen when you are sending an update to
- what you have previously sent.
- 
- `git format-patch` command follows the best current practice to
+ e-mail discussions.  Use of markers in addition to PATCH within
+ the brackets to describe the nature of the patch is also
+ encouraged.  E.g. [RFC PATCH] (where RFC stands for "request for
+ comments") is often used to indicate a patch needs further
+ discussion before being accepted, [PATCH v2], [PATCH v3] etc.
+ are often seen when you are sending an update to what you have
+ previously sent.
+ 
 -The "git format-patch" command follows the best current practice to
++The `git format-patch` command follows the best current practice to
  format the body of an e-mail message.  At the beginning of the
  patch should come your commit message, ending with the
  Signed-off-by: lines, and a line that consists of three dashes,