mirror of
git://git.gnupg.org/gnupg.git
synced 2025-07-03 22:56:33 +02:00
indent: Fix spelling
-- These are non-substantive corrections for minor spelling mistakes within the GnuPG codebase. With something like this applied to the codebase, and a judiciously tuned spellchecker integrated as part of a standard test suite, it should be possible to keep a uniform orthography within the project. GnuPG-bug-id: 7116
This commit is contained in:
parent
253a701ed7
commit
42b0e9558a
136 changed files with 233 additions and 233 deletions
|
@ -939,7 +939,7 @@ parse_bag_encrypted_data (struct p12_parse_ctx_s *ctx, tlv_parser_t tlv)
|
|||
if (!datalen)
|
||||
{
|
||||
err = gpg_error (GPG_ERR_DECRYPT_FAILED);
|
||||
ctx->badpass = 1; /* This is the most likley reason. */
|
||||
ctx->badpass = 1; /* This is the most likely reason. */
|
||||
goto bailout;
|
||||
}
|
||||
|
||||
|
@ -2546,7 +2546,7 @@ build_ecc_key_sequence (gcry_mpi_t *kparms, int mode, size_t *r_length)
|
|||
}
|
||||
|
||||
/* Unfortunately the private key D may come with a single leading
|
||||
* zero byte. This is becuase at some point it was treated as
|
||||
* zero byte. This is because at some point it was treated as
|
||||
* signed MPI and the code made sure that it is always interpreted
|
||||
* as unsigned. Fortunately we got the size of the curve and can
|
||||
* detect such a case reliable. */
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue