doc/SubmittingPatches.rst: use Google style guide for doc patches

Signed-off-by: Nathan Cutler <ncutler@suse.com>

diff --git a/SubmittingPatches.rst b/SubmittingPatches.rst
index 33345045b7f0e064c351fa40038acd87de092613..243ec83fd88a307ff79fa70cb027e0df80eb0938 100644 (file)
--- a/SubmittingPatches.rst
+++ b/SubmittingPatches.rst
@@ -12,11 +12,10 @@ The patch signing procedures and definitions are unmodified.
 SIGNING CONTRIBUTIONS
 =====================
 
-In order to keep the record of code attribution clean within the
-source repository, please follow these guidelines for signing 
-patches submitted to the project.  These definitions are taken
-from those used by the Linux kernel and many other open source
-projects.
+In order to keep the record of code attribution clean within the source
+repository, follow these guidelines for signing patches submitted to the
+project.  These definitions are taken from those used by the Linux kernel
+and many other open source projects.
 
 
 1. Sign your work
@@ -490,6 +489,9 @@ contact the component lead, who should arrange for the missing section
 to be created with sufficient detail for the patch submitter to
 document their changes.
 
+When writing and/or editing documentation, follow the Google Developer
+Documentation Style Guide: https://developers.google.com/style/
+
 6. Style check your changes
 ---------------------------