[25/35] Documentation: security: correct spelling

Commit Message

Randy Dunlap Jan. 27, 2023, 6:39 a.m. UTC

Correct spelling problems for Documentation/security/ as reported
by codespell.

Signed-off-by: Randy Dunlap <[e-mail]>
Cc: David Howells <[e-mail]>
Cc: Jarkko Sakkinen <[e-mail]>
Cc: [e-mail]
Cc: Paul Moore <[e-mail]>
Cc: James Morris <[e-mail]>
Cc: "Serge E. Hallyn" <[e-mail]>
Cc: [e-mail]
Cc: Jonathan Corbet <[e-mail]>
Cc: [e-mail]
---
 Documentation/security/digsig.rst       |    4 ++--
 Documentation/security/keys/core.rst    |    2 +-
 Documentation/security/secrets/coco.rst |    2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

Comments

David Howells Jan. 27, 2023, 6:59 a.m. UTC | #1

Randy Dunlap <[e-mail]> wrote:

> Correct spelling problems for Documentation/security/ as reported
> by codespell.
> 
> Signed-off-by: Randy Dunlap <[e-mail]>
> Cc: David Howells <[e-mail]>
> Cc: Jarkko Sakkinen <[e-mail]>
> Cc: [e-mail]
> Cc: Paul Moore <[e-mail]>
> Cc: James Morris <[e-mail]>
> Cc: "Serge E. Hallyn" <[e-mail]>
> Cc: [e-mail]
> Cc: Jonathan Corbet <[e-mail]>
> Cc: [e-mail]

Reviewed-by: David Howells <[e-mail]>

Patch

diff -- a/Documentation/security/digsig.rst b/Documentation/security/digsig.rst
--- a/Documentation/security/digsig.rst
+++ b/Documentation/security/digsig.rst
@@ -62,7 +62,7 @@  API currently includes only 1 function::
 	* digsig_verify() - digital signature verification with public key
 	* @keyring:	keyring to search key in
 	* @sig:	digital signature
-	* @sigen:	length of the signature
+	* @siglen:	length of the signature
 	* @data:	data
 	* @datalen:	length of the data
 	* @return:	0 on success, -EINVAL otherwise
@@ -82,7 +82,7 @@  The signing and key management utilities
 to generate signatures, to load keys into the kernel keyring.
 Keys can be in PEM or converted to the kernel format.
 When the key is added to the kernel keyring, the keyid defines the name
-of the key: 5D2B05FC633EE3E8 in the example bellow.
+of the key: 5D2B05FC633EE3E8 in the example below.
 
 Here is example output of the keyctl utility::
 
diff -- a/Documentation/security/keys/core.rst b/Documentation/security/keys/core.rst
--- a/Documentation/security/keys/core.rst
+++ b/Documentation/security/keys/core.rst
@@ -869,7 +869,7 @@  The keyctl syscall functions are:
 
 	 - ``char *hashname`` specifies the NUL terminated string identifying
 	   the hash used from the kernel crypto API and applied for the KDF
-	   operation. The KDF implemenation complies with SP800-56A as well
+	   operation. The KDF implementation complies with SP800-56A as well
 	   as with SP800-108 (the counter KDF).
 
 	 - ``char *otherinfo`` specifies the OtherInfo data as documented in
diff -- a/Documentation/security/secrets/coco.rst b/Documentation/security/secrets/coco.rst
--- a/Documentation/security/secrets/coco.rst
+++ b/Documentation/security/secrets/coco.rst
@@ -34,7 +34,7 @@  be use it for its own purposes.
 
 During the VM's launch, the virtual machine manager may inject a secret to that
 area.  In AMD SEV and SEV-ES this is performed using the
-``KVM_SEV_LAUNCH_SECRET`` command (see [sev]_).  The strucutre of the injected
+``KVM_SEV_LAUNCH_SECRET`` command (see [sev]_).  The structure of the injected
 Guest Owner secret data should be a GUIDed table of secret values; the binary
 format is described in ``drivers/virt/coco/efi_secret/efi_secret.c`` under
 "Structure of the EFI secret area".