Skip to content

docs: fix typos of multiple importance #11545

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
crStiv wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs: fix typos of multiple importance #11545

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions developer_key_publishing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

In the development life cycle, there are a number of points where it is useful to have a published [public key](https://en.wikipedia.org/wiki/Public-key_cryptography). Examples include build signing, Git commit signing, and communicating with other community members securely. Build signing in particular is a required part of the release process for the Celo blockchain client.

In support of these uses, [OpenPGP](https://www.openpgp.org/) public keys can be published to [celo.org](https://celo.org), where they can downloaded securely by anyone.
In support of these uses, [OpenPGP](https://www.openpgp.org/) public keys can be published to [celo.org](https://celo.org), where they can be downloaded securely by anyone.

If you want to read more about OpenPGP keys, including their structure and metadata, check out [Anatomy of a GPG Key by Dave Steele](https://davesteele.github.io/gpg/2014/09/20/anatomy-of-a-gpg-key/).

Expand Down Expand Up @@ -56,7 +56,7 @@ We recommend generating your developer key pair with a YubiKey. Generating your
3. `generate`
1. When asked if you want to backup your encryption key, specify `n` for no.
2. Specify an expiration date, for example `2y` for 2 years.
3. Enter you full name and `@clabs.co` email address when prompted.
3. Enter your full name and `@clabs.co` email address when prompted.
4. You may add a comment, but it is not required.
4. `quit`

Expand Down Expand Up @@ -155,7 +155,7 @@ This command will produce the signature file `doc.txt.asc` for `doc.txt`. The si

#### Signature Verification

A signature file produced with the method above can be verified by any user that possesses your public key with the following command.
A signature file produced with the method above can be verified by any user who possesses your public key with the following command.

```bash
gpg --verify doc.txt.asc doc.txt
Expand Down