docs: Update build examples to TF-PSA Crypto

Update build instruction to TF-PSA Crypto, which is now
the default Crypto.

And some other minor corrections and improvements.

Signed-off-by: Nicola Mazzucato <nicola.mazzucato@arm.com>
Change-Id: I0fec20adb9f8dcf5d37b3c190baf4c44b8efce3d

Author: nicola-mazzucato-arm

docs/building/tfm_build_instruction.rst

@@ -239,7 +239,7 @@ The following table lists the commonly used repos. For others, you can refer to
 +----------------+---------------------+-----------------------------------------------------+
 | Dependency     | Cmake variable      | Git repo URL                                        |
 +================+=====================+=====================================================+
-| Mbed Crypto    | MBEDCRYPTO_PATH     | https://github.com/Mbed-TLS/mbedtls                 |
+| TF-PSA Crypto  | TF_PSA_CRYPTO_PATH  | https://github.com/Mbed-TLS/TF-PSA-Crypto           |
 +----------------+---------------------+-----------------------------------------------------+
 | MCUboot        | MCUBOOT_PATH        | https://github.com/mcu-tools/mcuboot                |
 +----------------+---------------------+-----------------------------------------------------+
@@ -257,8 +257,8 @@ The recommended versions of the dependencies are listed in ``config/config_base.
    An alternative is to copy out the auto-downloaded repos under the ``<build_dir>/lib/ext``.
    They have been applied with patches and can be used directly.
 
-Example: building TF-M with local Mbed Crypto repo
---------------------------------------------------
+Example: building TF-M with local TF-PSA Crypto repo
+----------------------------------------------------
 
 Preparing a local repository consists of 2 steps: cloning and patching.
 This is only required to be done once. For dependencies without ``.patch``
@@ -267,15 +267,15 @@ cloning the repo and checking out the correct branch.
 
 .. code-block:: bash
 
-    cd <Mbed Crypto base folder>
-    git clone https://github.com/ARMmbed/mbedtls
-    cd mbedtls
-    git checkout <MBEDCRYPTO_VERSION> from <TF-M source dir>/config/config_base.cmake>
-    git apply <TF-M source dir>/lib/ext/mbedcrypto/*.patch
+    cd <TF-PSA Crypto base folder>
+    git clone https://github.com/Mbed-TLS/TF-PSA-Crypto
+    cd TF-PSA-Crypto
+    git checkout <TF_PSA_CRYPTO_VERSION> from <TF-M source dir>/config/config_base.cmake>
+    git apply <TF-M source dir>/lib/ext/tf-psa-crypto/*.patch
 
 .. Note::
 
-   ``<Mbed Crypto base folder>`` does not need to have any fixed position related
+   ``<TF-PSA Crypto base folder>`` does not need to have any fixed position related
    to the TF-M repo so alternative method to get prepared dependency repos is to
    let TF-M download it once and then copy them out of the ``build/lib/ext`` folder.
 
@@ -284,7 +284,7 @@ Now build TF-M binaries
 .. code-block:: bash
 
     cd <TF-M source dir>
-    cmake -S . -B build -DTFM_PLATFORM=arm/mps2/an521 -DMBEDCRYPTO_PATH=<Mbed Crypto base folder>/mbedtls
+    cmake -S . -B build -DTFM_PLATFORM=arm/mps2/an521 -DTF_PSA_CRYPTO_PATH=<TF-PSA Crypto base folder>/tf-psa-crypto
     cmake --build build -- install
 
 .. _Building NSPE:
@@ -314,6 +314,7 @@ will have the following structure:
     ├── cmake
     ├── config
     ├── image_signing
+    ├── initial_attestation
     ├── interface
     ├── platform
     └── CMakeLists.txt
@@ -325,15 +326,16 @@ These folders have the following content:
 - **cmake** - CMake scripts like SPE configuration and :ref:`NSPE toolchains`.
 - **config** - Configuration files
 - **image_signing** - binary image signing tool and keys.
+- **initial_attestation** - attestation interface APIs.
 - **interface** - PSA interface exposed by SPE.
 - **platform** - source code for a selected hardware platform.
 - **CMakeLists.txt** - CMake script for the artifacts integration in NSPE.
 
 The content of ``<Artifact Dir>`` is an exported directory for integration with CMake projects.
 
 .. Note::
-    Attempting to change any file in <Artifact Dir> may cause incompatibility issues.
-    Instead, please change the corresponding file in the <TF-M source dir>.
+    Attempting to change any file in ``<Artifact Dir>`` may cause incompatibility issues.
+    Instead, please change the corresponding file in the ``<TF-M source dir>``.
 
 .. _NSPE toolchains: