mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: [PATCH v1 5/5] maintainer-pgp-guide: minor wording tweaks
Date: Thu, 28 Jul 2022 16:57:08 -0400	[thread overview]
Message-ID: <20220727-docs-pgp-guide-v1-5-c48fb06cb9af@linuxfoundation.org> (raw)
In-Reply-To: <20220727-docs-pgp-guide-v1-0-c48fb06cb9af@linuxfoundation.org>

Tweak some wording to remove redundant information or fix spacing.

Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>

diff --git a/Documentation/process/maintainer-pgp-guide.rst b/Documentation/process/maintainer-pgp-guide.rst
index 2ce38e5d547d..ea74c87d09d8 100644
--- a/Documentation/process/maintainer-pgp-guide.rst
+++ b/Documentation/process/maintainer-pgp-guide.rst
@@ -265,9 +265,7 @@ home, such as your bank vault.
     Your printer is probably no longer a simple dumb device connected to
     your parallel port, but since the output is still encrypted with
     your passphrase, printing out even to "cloud-integrated" modern
-    printers should remain a relatively safe operation. One option is to
-    change the passphrase on your master key immediately after you are
-    done with paperkey.
+    printers should remain a relatively safe operation.
 
 Back up your whole GnuPG directory
 ----------------------------------
@@ -311,7 +309,7 @@ Remove the Certify key from your homedir
 ----------------------------------------
 
 The files in our home directory are not as well protected as we like to
-think.  They can be leaked or stolen via many different means:
+think. They can be leaked or stolen via many different means:
 
 - by accident when making quick homedir copies to set up a new workstation
 - by systems administrator negligence or malice

-- 
b4 0.10.0-dev-49460

  parent reply	other threads:[~2022-07-28 20:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 20:57 [PATCH v1 0/5] Update the maintainer PGP guide Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 1/5] maintainer-pgp-guide: use key terminology consistent with upstream Konstantin Ryabitsev
2022-07-30 13:12   ` Wu XiangCheng
2022-08-02 17:07     ` Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 2/5] maintainer-pgp-guide: remove keyserver instructions Konstantin Ryabitsev
2022-07-29  1:47   ` Bagas Sanjaya
2022-08-02 17:21     ` Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 3/5] maintainer-pgp-guide: update ECC support information Konstantin Ryabitsev
2022-07-29  9:11   ` Bagas Sanjaya
2022-08-02 17:16     ` Konstantin Ryabitsev
2022-07-28 20:57 ` [PATCH v1 4/5] maintainer-pgp-guide: add a section on PGP-signed patches Konstantin Ryabitsev
2022-07-28 20:57 ` Konstantin Ryabitsev [this message]
2022-07-29 22:55   ` [PATCH v1 5/5] maintainer-pgp-guide: minor wording tweaks Randy Dunlap
2022-08-02 17:09     ` Konstantin Ryabitsev
2022-08-02  9:07 ` [PATCH v1 0/5] Update the maintainer PGP guide Alexander Dahl
2022-08-02 17:00   ` Konstantin Ryabitsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220727-docs-pgp-guide-v1-5-c48fb06cb9af@linuxfoundation.org \
    --to=konstantin@linuxfoundation.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome