chore: fix format

docs/developer/08. Certificate Management/02. Certificate Deletion.md

@@ -37,11 +37,12 @@ n/a
 <br>
 
 When running the endpoint - first the backend validates if the certificate is assigned to the same company_id as the acting user company_id
-  - if yes, the deletion will get processed (details see below)
-  - if not; the process is stopped and an error is responded
+
+- if yes, the deletion will get processed (details see below)
+- if not; the process is stopped and an error is responded
 
 In the successful validation case: the respective document inside the table portal.documents is set to "INACTIVE" and the "last_date_changed" date is updated as well as the "last_editor_id"
-Afterwards the status inside the table portal.company_certificates is getting set to "INACTIVE" 
+Afterwards the status inside the table portal.company_certificates is getting set to "INACTIVE"
 
 <br>
 <br>

docs/developer/Technical Documentation/Interface Contracts/Self Description.md

@@ -22,8 +22,10 @@ In the current implementation level, self-descriptions are considered in the fol
 
 ## Architecture Overview
 
-![SD-Factory - Portal interaction](../../../static/sdfactory-portal-interactions.png)
-
+<br>
+<img width="927" alt="image" src="https://raw.githubusercontent.com/eclipse-tractusx/portal-assets/main/docs/static/sdfactory-portal-interactions.png">
+<br>
+<br>
 
 ## Description of the functional interface (WHAT)
 
@@ -35,8 +37,8 @@ The json ld file is supposed to get stored - for now normal db document storage
 ## Description of the physical interfaces (HOW)
 
 Portal is pushing the self description via an REST API "POST" developed under the portal context.
-Factory receives the information and transforms it to the self-description without signature. Then unsigned Self-Description is passed 
-to the Validation Service, which checks parameter values and signs Verifiable Credentials. This process is performed 
+Factory receives the information and transforms it to the self-description without signature. Then unsigned Self-Description is passed
+to the Validation Service, which checks parameter values and signs Verifiable Credentials. This process is performed
 asynchronously. The result is sent to the portal with an "content" section. The content section is getting stored as json file in the portal db.
 <br>
 <br>