From bf7a98b791fe21f1ee5d553f4dfe1d1cbfe3ef8a Mon Sep 17 00:00:00 2001 From: Gilles Peskine Date: Fri, 22 Feb 2019 16:42:11 +0100 Subject: [PATCH] Fix typos found in PSA Crypto API 1.0 beta2 before publication --- include/psa/crypto.h | 2 +- include/psa/crypto_values.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/include/psa/crypto.h b/include/psa/crypto.h index dd4599687b..e7d0ecda74 100644 --- a/include/psa/crypto.h +++ b/include/psa/crypto.h @@ -754,7 +754,7 @@ psa_status_t psa_export_public_key(psa_key_handle_t handle, * to another. The target key retains its lifetime and location. * * In an implementation where slots have different ownerships, - * this functin may be used to share a key with a different party, + * this function may be used to share a key with a different party, * subject to implementation-defined restrictions on key sharing. * In this case \p constraint would typically prevent the recipient * from exporting the key. diff --git a/include/psa/crypto_values.h b/include/psa/crypto_values.h index a47695c2e8..e0cc5446fb 100644 --- a/include/psa/crypto_values.h +++ b/include/psa/crypto_values.h @@ -187,7 +187,7 @@ * the global integrity of the keystore. Depending on the global * integrity guarantees offered by the implementation, access to other * data may or may not fail even if the data is still readable but - * its integrity canont be guaranteed. + * its integrity cannot be guaranteed. * * Implementations should only use this error code to report a * permanent storage corruption. However application writers should