suzanne.soy/qubes-doc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

correct spelling

Browse Source 
this addresses
https://github.com/QubesOS/qubes-doc/pull/666#issuecomment-401643800
This commit is contained in:
Nicco Kunzmann 2018-07-02 10:51:10 +02:00 committed by GitHub
parent f08dea7320
commit f570d93b1c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
basics_dev/code-signing.md
View File

@ -136,7 +136,7 @@ Code Signature Checks
--------------------- ---------------------
The [signature-checker] checks if code contributions are signed. 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? 1. Is the commit signed?
If the commit is not signed, you can see the message 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: 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: You can use this command to create a new signed commit:
``` ```
git commit --amend -S git commit --amend -S