Docs: Correct some spelling error
Change-Id: I0a7006dc816b204284bce2793187942250720a18
Signed-off-by: Edison Ai <edison.ai@arm.com>
diff --git a/docs/design_documents/secure_boot_rollback_protection.rst b/docs/design_documents/secure_boot_rollback_protection.rst
index f6b4c55..711fac3 100644
--- a/docs/design_documents/secure_boot_rollback_protection.rst
+++ b/docs/design_documents/secure_boot_rollback_protection.rst
@@ -82,7 +82,7 @@
The value of the security counter is a security critical data. Any change in
its value has a security implication. Therefore it must be in the integrity
protected part of the image manifest. Because the image header is almost fully
-utilised (few unused fields) and the change of image header structure could
+utilized (few unused fields) and the change of image header structure could
lead to compatibility issues between boot loader and runtime software, it is
proposed to extend the integrity protection to some part of the TLV section.
One of the unused fields in the image header can be used to store the size of
@@ -200,4 +200,4 @@
--------------
-*Copyright (c) 2019, Arm Limited. All rights reserved.*
+*Copyright (c) 2019-2020, Arm Limited. All rights reserved.*
diff --git a/docs/design_documents/source_structure.rst b/docs/design_documents/source_structure.rst
index 1b71215..42641a1 100644
--- a/docs/design_documents/source_structure.rst
+++ b/docs/design_documents/source_structure.rst
@@ -6,8 +6,8 @@
:Contact: tf-m@lists.trustedfirmware.org
.. note::
- Refernce the document :doc:`Glossary </docs/reference/glossary>` for terms and
- abbreviations.
+ Reference the document :doc:`Glossary </docs/reference/glossary>` for terms
+ and abbreviations.
************
Introduction
@@ -29,7 +29,7 @@
The description of the source structure is broken down into subsections, each
subsection introduces one detailed folder.
-Root Direcotry
+Root Directory
==============
This table describes the structure under the root directory with part of
possible folders. Note that the ``Detailed`` field indicates if the folder is
diff --git a/docs/design_documents/symmetric_initial_attest.rst b/docs/design_documents/symmetric_initial_attest.rst
index a763433..afd2fd2 100644
--- a/docs/design_documents/symmetric_initial_attest.rst
+++ b/docs/design_documents/symmetric_initial_attest.rst
@@ -15,7 +15,7 @@
Symmetric key algorithm based Initial Attestation
(*symmetric Initial Attestation* for short) signs and verifies Initial
-Attestation Token (IAT) with a symmetric crypotgraphy signature scheme, such as
+Attestation Token (IAT) with a symmetric cryptography signature scheme, such as
HMAC.
It can reduce TF-M binary size and memory footprint on ultra-constrained devices
without integrating asymmetric ciphers.
diff --git a/docs/design_documents/tfm_its_512_flash.rst b/docs/design_documents/tfm_its_512_flash.rst
index 6ce144d..aa58c2b 100644
--- a/docs/design_documents/tfm_its_512_flash.rst
+++ b/docs/design_documents/tfm_its_512_flash.rst
@@ -12,7 +12,7 @@
The proposal is describing a mechanism to enable the use of larger flash
devices, imposing a requirement for word-aligned full-block program operations,
-in Trusted Firmare-M.
+in Trusted Firmware-M.
Requirements
diff --git a/docs/design_documents/tfm_non-secure_interrupt_handling.rst b/docs/design_documents/tfm_non-secure_interrupt_handling.rst
index fd10fb1..3b0b143 100644
--- a/docs/design_documents/tfm_non-secure_interrupt_handling.rst
+++ b/docs/design_documents/tfm_non-secure_interrupt_handling.rst
@@ -35,7 +35,7 @@
1. ``AIRCR.PRIS`` is set to 1 during TF-M core initialisation. This
de-prioritizes Non-secure exceptions compared to Secure exceptions, so that
- they cannot interupt Secure Handler mode. the ``AIRCR.PRIS`` bit remains set
+ they cannot interrupt Secure Handler mode. the ``AIRCR.PRIS`` bit remains set
during TF-M run. The bit is set in the function
.. code-block:: c
@@ -233,8 +233,8 @@
The caller client ID can be saved in the function
``void tfm_psa_ipc_request_handler(uint32_t svc_ctx[])`` depending on the return
value of the PSA API function. (Doesn't execute any Secure service code, only
-sets signals, and triggrs scheduling. If the return value is success, that means
-a scheduling is to happen, and a secure service is about to be entered.)
+sets signals, and triggers scheduling. If the return value is success, that
+means a scheduling is to happen, and a secure service is about to be entered.)
Check client ID on Secure service return
----------------------------------------
@@ -312,7 +312,7 @@
NS execute test scenario Do nothing
============ ===================== ===========================================
-The test is successful if NS execute test scenario returns
+The test is successful if NS execute test scenario returns.
Advanced scenarios
==================
diff --git a/docs/design_documents/tfm_secure_partition_runtime_library.rst b/docs/design_documents/tfm_secure_partition_runtime_library.rst
index 69eda49..4e071ee 100644
--- a/docs/design_documents/tfm_secure_partition_runtime_library.rst
+++ b/docs/design_documents/tfm_secure_partition_runtime_library.rst
@@ -47,7 +47,7 @@
- **Security first** - SPRTL is designed for security and it may come with
some performance loss.
-API Catagories
+API Categories
==============
Several known types of functions are included in SPRTL:
@@ -167,7 +167,7 @@
}
This is the simplest case of encapsulating PSA Client API. If a RoT Service API
-is contect heavy, then, the encapsulation can be changed to include a connection
+is connect heavy, then, the encapsulation can be changed to include a connection
handle inside a context data structure. This context data structure type is
defined in RoT Service headers and the instance is allocated by API caller since
API implementation does not have private data.