[PATCH 1/2] doc: fix small issues in SubmittingPatches

From

Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>

Date

Aug 1, 2017, 16:05 UTC

Message-ID

<20170801160539.5587-1-kaarticsivaraam91196@gmail.com>

In-Reply-To

<CAGZ79kYg9jQ3kaKnNEJCH9fde=ar1KPiUr7=X+TguNc0Twqdzg@mail.gmail.com>

Use double quotes to quote a git command for consistency.

Signed-off-by: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
---
 Documentation/SubmittingPatches | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index 558d465b6..886fe3650 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -293,7 +293,7 @@ then you just add a line saying
 
         Signed-off-by: Random J Developer <random@developer.example.org>
 
-This line can be automatically added by Git if you run the git-commit
+This line can be automatically added by Git if you run the "git commit"
 command with the -s option.
 
 Notice that you can place your own Signed-off-by: line when
@@ -380,7 +380,7 @@ their trees themselves.
 Know the status of your patch after submission
 
 * You can use Git itself to find out when your patch is merged in
-  master. 'git pull --rebase' will automatically skip already-applied
+  master. "git pull --rebase" will automatically skip already-applied
   patches, and will let you know. This works only if you rebase on top
   of the branch in which your patch has been merged (i.e. it will not
   tell you if your patch is merged in pu if you rebase on top of

-- 
2.14.0.rc1.434.g6eded367a