Merge pull request #102 from athoelke/fix-typos

Fix typos: remove duplicated words

Author: athoelke

doc/crypto/api/keys/attributes.rst

@@ -41,7 +41,7 @@ Managing key attributes
 
         An implementations can report attribute values that are equivalent to the original one, but have a different encoding. For example, an implementation can use a more compact representation for types where many bit-patterns are invalid or not supported, and store all values that it does not support as a special marker value. In such an implementation, after setting an invalid value, the corresponding get function returns an invalid value which might not be the one that was originally stored.
 
-    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in in implementation-specific behavior, and are non-portable.
+    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in implementation-specific behavior, and are non-portable.
 
     An attribute object can contain references to auxiliary resources, for example pointers to allocated memory or indirect references to pre-calculated values. In order to free such resources, the application must call `psa_reset_key_attributes()`. As an exception, calling `psa_reset_key_attributes()` on an attribute object is optional if the object has only been modified by the following functions since it was initialized or last reset with `psa_reset_key_attributes()`:
 

doc/crypto/api/ops/aead.rst

@@ -382,7 +382,7 @@ Multi-part AEAD operations
             psa_aead_operation_t operation;
             operation = psa_aead_operation_init();
 
-    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in in implementation-specific behavior, and are non-portable.
+    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in implementation-specific behavior, and are non-portable.
 
 .. macro:: PSA_AEAD_OPERATION_INIT
     :definition: /* implementation-defined value */

doc/crypto/api/ops/ciphers.rst

@@ -439,7 +439,7 @@ Multi-part cipher operations
             psa_cipher_operation_t operation;
             operation = psa_cipher_operation_init();
 
-    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in in implementation-specific behavior, and are non-portable.
+    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in implementation-specific behavior, and are non-portable.
 
 .. macro:: PSA_CIPHER_OPERATION_INIT
     :definition: /* implementation-defined value */

doc/crypto/api/ops/hashes.rst

@@ -309,7 +309,7 @@ Multi-part hashing operations
             psa_hash_operation_t operation;
             operation = psa_hash_operation_init();
 
-    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in in implementation-specific behavior, and are non-portable.
+    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in implementation-specific behavior, and are non-portable.
 
 .. macro:: PSA_HASH_OPERATION_INIT
     :definition: /* implementation-defined value */

doc/crypto/api/ops/kdf.rst

@@ -399,7 +399,7 @@ Key derivation functions
             psa_key_derivation_operation_t operation;
             operation = psa_key_derivation_operation_init();
 
-    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in in implementation-specific behavior, and are non-portable.
+    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in implementation-specific behavior, and are non-portable.
 
 .. macro:: PSA_KEY_DERIVATION_OPERATION_INIT
     :definition: /* implementation-defined value */

doc/crypto/api/ops/macs.rst

@@ -318,7 +318,7 @@ Multi-part MAC operations
             psa_mac_operation_t operation;
             operation = psa_mac_operation_init();
 
-    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in in implementation-specific behavior, and are non-portable.
+    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in implementation-specific behavior, and are non-portable.
 
 .. macro:: PSA_MAC_OPERATION_INIT
     :definition: /* implementation-defined value */

doc/ext-pake/api/pake.rst

@@ -366,7 +366,7 @@ A PAKE cipher suite is required when setting up a PAKE operation in `psa_pake_se
 
         An implementations can report attribute values that are equivalent to the original one, but have a different encoding. For example, an implementation can use a more compact representation for attributes where many bit-patterns are invalid or not supported, and store all values that it does not support as a special marker value. In such an implementation, after setting an invalid value, the corresponding get function returns an invalid value which might not be the one that was originally stored.
 
-    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in in implementation-specific behavior, and are non-portable.
+    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in implementation-specific behavior, and are non-portable.
 
     Before calling any function on a PAKE cipher suite object, the application must initialize it by any of the following means:
 
@@ -691,7 +691,7 @@ Multi-part PAKE operations
             psa_pake_operation_t operation;
             operation = psa_pake_operation_init();
 
-    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in in implementation-specific behavior, and are non-portable.
+    This is an implementation-defined type. Applications that make assumptions about the content of this object will result in implementation-specific behavior, and are non-portable.
 
 .. macro:: PSA_PAKE_OPERATION_INIT
     :definition: /* implementation-defined value */

doc/fwu/appendix/variations.rst

@@ -48,7 +48,7 @@ See :secref:`variations-volatile` for example state models for a component that
 Component that requires a reboot, but no trial
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-If a component does not require testing before committing the update, the the TRIAL and REJECTED states are not used.
+If a component does not require testing before committing the update, the TRIAL and REJECTED states are not used.
 
 *  The reboot that installs the firmware will transition the component to UPDATED on success, or FAILED on failure, unless the target state is volatile, in which case the reboot will transition the component to READY.
 *  The ``accept`` operation is never used.

doc/fwu/terms

@@ -82,7 +82,7 @@
 
    A component with volatile staging does not preserve a firmware image that is in the :term:`staging area` after a reboot.
 
-   A component without volatile staging preserves a prepared candidate firmware image after a reboot. It is :scterm:`implementation defined` whether a partially prepared image in in the staging area is retained after a system reset.
+   A component without volatile staging preserves a prepared candidate firmware image after a reboot. It is :scterm:`implementation defined` whether a partially prepared image in the staging area is retained after a system reset.
 
    See `PSA_FWU_FLAG_VOLATILE_STAGING`.