From 18e76e7eefd484c5f14d64beaeee98d70b12cee9 Mon Sep 17 00:00:00 2001 From: Gilles Peskine Date: Wed, 26 Oct 2022 14:43:13 +0200 Subject: [PATCH] typo Signed-off-by: Gilles Peskine --- docs/architecture/psa-crypto-implementation-structure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/architecture/psa-crypto-implementation-structure.md b/docs/architecture/psa-crypto-implementation-structure.md index e7282381e1..3fe074f352 100644 --- a/docs/architecture/psa-crypto-implementation-structure.md +++ b/docs/architecture/psa-crypto-implementation-structure.md @@ -112,7 +112,7 @@ If a mechanism requires new functions, they should follow the design guidelines Functions that are part of the current or upcoming API are declared in `include/psa/crypto.h`, apart from structure accessors defined in `include/psa/crypto_struct.h`. Functions that have output buffers have associated sufficient-output-size macros in `include/psa/crypto_sizes.h`. -Constants (algorithm identifiers, key type identifiers, etc.) and associated desctructor macros (e.g. `PSA_IS_xxx()`) are defined in `include/psa/crypto_values.h`. +Constants (algorithm identifiers, key type identifiers, etc.) and associated destructor macros (e.g. `PSA_IS_xxx()`) are defined in `include/psa/crypto_values.h`. Functions and macros that are not intended for standardization, or that are at a stage where the draft standard might still evolve significantly, are declared in `include/psa/crypto_extra.h`.