SubmittingPatches: added inline markup to important references

Signed-off-by: James McClune <jmcclune@mcclunetechnologies.net>

diff --git a/SubmittingPatches.rst b/SubmittingPatches.rst
index 8ee0d1879ca57a92ffd1301131797a80a2382e91..a13191d8572434d8a96c6264887a1e7349abc11b 100644 (file)
--- a/SubmittingPatches.rst
+++ b/SubmittingPatches.rst
@@ -152,7 +152,7 @@ have been included in the discussion
 --------------------------------------------------------------
 
 If this patch fixes a problem reported by somebody else, consider adding a
-Reported-by: tag to credit the reporter for their contribution. This tag should
+``Reported-by:`` tag to credit the reporter for their contribution. This tag should
 not be added without the reporter's permission, especially if the problem was
 not reported in a public forum. That said, if we diligently credit our bug
 reporters, they will, hopefully, be inspired to help us again in the future.
@@ -254,7 +254,7 @@ email list to ensure your submission is noticed.
 When addressing review comments, can should either add additional patches to
 your branch or (better yet) squash those changes into the relevant commits so
 that the sequence of changes is "clean" and gets things right the first time.
-The 'git rebase -i' command is very helpful in this process. Once you have
+The ``git rebase -i`` command is very helpful in this process. Once you have
 updated your local branch, you can simply force-push to the existing branch
 in your public repository that is referenced by the pull request with