[Documentation] Remove links to non-existent images

Author: TofMassilia13320

Documentation/resources/Markdown/03_Project_examples_description/Command_AC_provisioning/STSAFE-A120_Command_AC_provisioning.md

@@ -4,8 +4,6 @@ This example demonstrates how to configure command access conditions (AC) and en
 
 Access condition provisioning is a critical security configuration that determines which commands can be executed freely, which require host authentication (via host session), and which are forbidden. This configuration is typically performed during device personalization and cannot be changed afterward once the change right is disabled.
 
-![STSAFE-A120_Command_AC_provisioning](./STSAFE-A120_Command_AC_provisioning.png)
-
 ## Example Flowchart
 
 The following flowchart illustrates the command AC provisioning process:

Documentation/resources/Markdown/03_Project_examples_description/Key_pair_generation_EDWARDS_25519/STSAFE-A120_Key_pair_generation_EDWARDS_25519.md

@@ -4,8 +4,6 @@ This example demonstrates how to generate an EdDSA (Edwards-curve Digital Signat
 
 Edwards-25519, also known as Ed25519, is based on the Curve25519 elliptic curve and provides approximately 128-bit security. It is designed to be fast, secure against timing attacks, and requires no random number generation during the signing process, making it particularly suitable for embedded and IoT applications.
 
-![STSAFE-A120_Key_pair_generation_EDWARDS_25519](./STSAFE-A120_Key_pair_generation_EDWARDS_25519.png)
-
 ## Example Flowchart
 
 The following flowchart illustrates the Ed25519 key pair generation and signature verification process:

Documentation/resources/Markdown/03_Project_examples_description/Key_pair_generation_NIST_P256/STSAFE-A120_Key_pair_generation_NIST_P256.md

@@ -4,8 +4,6 @@ This example demonstrates how to generate an ECC (Elliptic Curve Cryptography) k
 
 The NIST P-256 curve (also known as secp256r1 or prime256v1) is a standardized elliptic curve recommended by NIST for cryptographic use. It provides 128-bit security with relatively small key sizes (256 bits), making it suitable for resource-constrained embedded systems.
 
-![STSAFE-A120_Key_pair_generation_NIST_P256](./STSAFE-A120_Key_pair_generation_NIST_P256.png)
-
 ## Example Flowchart
 
 The following flowchart illustrates the key pair generation and signature verification process:

Documentation/resources/Markdown/03_Project_examples_description/Project_template/STSAFE-A120_Project_template.md

@@ -4,8 +4,6 @@ This template provides a minimal starting point for developing custom STSAFE-A12
 
 The template demonstrates the essential setup steps required for any STSAFE-A120 application, including terminal initialization and the main application loop structure. Developers can use this as a foundation and add their specific functionality.
 
-![STSAFE-A120_Project_template](./STSAFE-A120_Project_template.png)
-
 ## Example Flowchart
 
 The following flowchart illustrates the basic template structure:

Documentation/resources/Markdown/03_Project_examples_description/Symmetric_key_provisioning_control_fields/STSAFE-A120_Symmetric_key_provisioning_control_fields.md

@@ -4,8 +4,6 @@ This example demonstrates how to configure the provisioning control fields for s
 
 Control fields provide fine-grained control over how symmetric keys can be installed into the STSAFE-A120, including whether keys can be written in plaintext, wrapped (encrypted), or derived via ECDHE (Elliptic Curve Diffie-Hellman Ephemeral). This configuration is critical for establishing the security posture of the device.
 
-![STSAFE-A120_Symmetric_key_provisioning_control_fields](./STSAFE-A120_Symmetric_key_provisioning_control_fields.png)
-
 ## Example Flowchart
 
 The following flowchart illustrates the control field configuration process:

Documentation/resources/Markdown/03_Project_examples_description/Symmetric_key_provisioning_wrapped_AES-128_CMAC/STSAFE-A120_Symmetric_key_provisioning_wrapped_AES-128_CMAC.md

@@ -4,8 +4,6 @@ This example demonstrates how to securely provision an AES-128 symmetric key int
 
 Wrapped key provisioning provides a secure method for transferring symmetric keys to the STSAFE-A120 without exposing them in plaintext on the communication bus. The key is encrypted using a Key Encryption Key (KEK) derived from the host secure session, ensuring end-to-end protection during the provisioning process.
 
-![STSAFE-A120_Symmetric_key_provisioning_wrapped_AES-128_CMAC](./STSAFE-A120_Symmetric_key_provisioning_wrapped_AES-128_CMAC.png)
-
 ## Example Flowchart
 
 The following flowchart illustrates the wrapped key provisioning and CMAC operation:

Documentation/resources/Markdown/03_Project_examples_description/Symmetric_key_provisioning_wrapped_AES-256_CCM/STSAFE-A120_Symmetric_key_provisioning_wrapped_AES-256_CCM.md

@@ -4,8 +4,6 @@ This example demonstrates how to securely provision an AES-256 symmetric key int
 
 Wrapped key provisioning protects the symmetric key during transfer by encrypting it with a Key Encryption Key (KEK) derived from the host secure session. This ensures the key is never exposed in plaintext on the communication bus, providing production-grade security for key management.
 
-![STSAFE-A120_Symmetric_key_provisioning_wrapped_AES-256_CCM](./STSAFE-A120_Symmetric_key_provisioning_wrapped_AES-256_CCM.png)
-
 ## Example Flowchart
 
 The following flowchart illustrates the wrapped key provisioning and CCM* operation: