All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.01.org
Subject: [PATCH] manpages: replace shorthand words
Date: Mon, 28 Oct 2019 09:10:13 -0700	[thread overview]
Message-ID: <20191028161013.7725-1-prestwoj@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]

Replaces cases of 'certs' with 'certificates', and 8021x with IEEE 802.1x
---
 src/iwd.network.rst | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/src/iwd.network.rst b/src/iwd.network.rst
index 33efd3f4..4a843b7e 100644
--- a/src/iwd.network.rst
+++ b/src/iwd.network.rst
@@ -234,10 +234,10 @@ authentication configuration.
 Embedded PEMs
 -------------
 
-Rather than including an absolute path to a PEM file (for certs or keys), the
-PEM itself can be included inside the settings file and referenced directly.
-This allows 8021x network provisioning using a single file without any
-references to certificates/keys on the system.
+Rather than including an absolute path to a PEM file (for certificates and
+keys), the PEM itself can be included inside the settings file and referenced
+directly. This allows IEEE 802.1x network provisioning using a single file
+without any references to certificates or keys on the system.
 
 An embedded PEM can appear anywhere in the settings file using the following
 format (this example the PEM is named 'my_ca_cert'):
@@ -255,8 +255,8 @@ elsewhere in the settings file by prefixing the value with 'embed:'
 
 EAP-TLS-CACert=embed:my_ca_cert
 
-This is not limited to CA Certs either. Client certs, client keys (encrypted
-or not), and certificate chains can be included.
+This is not limited to CA Certificates either. Client certificates, client keys
+(encrypted or not), and certificate chains can be included.
 
 SEE ALSO
 ========
-- 
2.17.1

             reply	other threads:[~2019-10-28 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-28 16:10 James Prestwood [this message]
2019-10-28 15:45 ` [PATCH] manpages: replace shorthand words Denis Kenzior

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=20191028161013.7725-1-prestwoj@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=iwd@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.