diff --git a/g10/cpr.c b/g10/cpr.c index 3d39d6bda..d502e8b52 100644 --- a/g10/cpr.c +++ b/g10/cpr.c @@ -62,7 +62,7 @@ progress_cb (void *ctx, const char *what, int printchar, /* Return true if the status message NO may currently be issued. We - need this to avoid syncronisation problem while auto retrieving a + need this to avoid synchronization problem while auto retrieving a key. There it may happen that a status NODATA is issued for a non available key and the user may falsely interpret this has a missing signature. */ diff --git a/kbx/keybox-blob.c b/kbx/keybox-blob.c index 0bcd4a323..8ac67afbe 100644 --- a/kbx/keybox-blob.c +++ b/kbx/keybox-blob.c @@ -134,7 +134,7 @@ Note that this value matches TRUST_FLAG_REVOKED - u16 RFU - u32 Recheck_after - - u32 Latest timestamp in the keyblock (useful for KS syncronsiation?) + - u32 Latest timestamp in the keyblock (useful for KS synchronization?) - u32 Blob created at - u32 [NRES] Size of reserved space (not including this field) - bN Reserved space of size NRES for future use. @@ -144,7 +144,7 @@ - bN Space for the keyblock or certificate. - bN RFU. This is the remaining space after keyblock and before the checksum. It is not covered by the checksum. - - b20 SHA-1 checksum (useful for KS syncronisation?) + - b20 SHA-1 checksum (useful for KS synchronization?) Note, that KBX versions before GnuPG 2.1 used an MD5 checksum. However it was only created but never checked. Thus we do not expect problems if we switch to SHA-1. If diff --git a/scd/ccid-driver.c b/scd/ccid-driver.c index 657766e30..e092a2b9a 100644 --- a/scd/ccid-driver.c +++ b/scd/ccid-driver.c @@ -2963,7 +2963,7 @@ ccid_transceive_apdu_level (ccid_driver_t handle, bit 7 1 bit 6 1 bit 5 clear=request,set=response - bit 4..0 0 = resyncronisation request + bit 4..0 0 = resynchronization request 1 = information field size request 2 = abort request 3 = extension of BWT request