From f570d93b1cf0e0273941cb6f1b793f119b496e24 Mon Sep 17 00:00:00 2001 From: Nicco Kunzmann Date: Mon, 2 Jul 2018 10:51:10 +0200 Subject: [PATCH] correct spelling this addresses https://github.com/QubesOS/qubes-doc/pull/666#issuecomment-401643800 --- basics_dev/code-signing.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/basics_dev/code-signing.md b/basics_dev/code-signing.md index d9035f22..018dcf17 100644 --- a/basics_dev/code-signing.md +++ b/basics_dev/code-signing.md @@ -136,7 +136,7 @@ Code Signature Checks --------------------- The [signature-checker] checks if code contributions are signed. -Although GitHub adds a little green `Verified` button next to the commit, the [signature-checker] uses this algorithm to check if a commit is currectly signed: +Although GitHub adds a little green `Verified` button next to the commit, the [signature-checker] uses this algorithm to check if a commit is correctly signed: 1. Is the commit signed? If the commit is not signed, you can see the message @@ -151,7 +151,7 @@ Although GitHub adds a little green `Verified` button next to the commit, the [s In this case, you have several options to sign the commit: -1. Amend the commit and repace it with a signed commit. +1. Amend the commit and replace it with a signed commit. You can use this command to create a new signed commit: ``` git commit --amend -S