chore: fix format and typos

eclipse-tractusx · Feb 28, 2024 · 8d80d0e · 8d80d0e
1 parent 4bb7ef7
commit 8d80d0e
Show file tree

Hide file tree

Showing 2 changed files with 21 additions and 22 deletions.
diff --git a/docs/developer/00. Personas/05. Onboarding Service Provider.md b/docs/developer/00. Personas/05. Onboarding Service Provider.md
@@ -1,16 +1,16 @@
 ## Onboarding Service Provider (OSP)
 
-The onboarding service provider is a standalone dataspace participant which has as goal to scale the dataspace fast and to provide either a unique onboarding flow for the customer or interacts as OSP to provide a quick and easy connection for their existing network customers to the catena-x dataspace.
+The onboarding service provider is a standalone dataspace participant which has as goal to scale the dataspace fast and to provide either a unique onboarding flow for the customer or interacts as OSP to provide a quick and easy connection for their existing network customers to the Catena-X dataspace.
 In the current implementation stage the OSP is responsible for the
 
 <br>
 
 - [Role Description](#role-description)
-	- [MUST Services](#must-services)
-	- [Outlook Future Releases](#outlook-future-releases)
+  - [MUST Services](#must-services)
+  - [Outlook Future Releases](#outlook-future-releases)
 - [Become an OSP](#become-an-osp)
-	- [Certification](#certification)
-	- [Network Role](#network-role)
+  - [Certification](#certification)
+  - [Network Role](#network-role)
 - [Register your customer IdP](#register-your-customer-idp)
 - [Create External Registrations](#create-external-registrations)
 - [Receive registration status](#receive-registration-status)
@@ -27,17 +27,17 @@ For smooth operations, the OSP must provide comprehensive technical documentatio
 
 #### MUST Services
 
-* An OSP must implement an IAM synchronization with CSP-As, the CSP-B, and OSPs to provide its customers with access to the data space.  
-* An OSP must integrate and use CSP-B services to access their identity (e. g., identity wallet) and enable data exchange.
+- An OSP must implement an IAM synchronization with CSP-As, the CSP-B, and OSPs to provide its customers with access to the data space.
+- An OSP must integrate and use CSP-B services to access their identity (e. g., identity wallet) and enable data exchange.
 
 #### Outlook Future Releases
 
-* An OSP must integrate and use the GAIA-X Digital Clearing House to validate e. g., the Legal Person Self-Description.  
-* An OSP CAN offer a wallet solution for their customers; if not offered, the wallet of the connected CSP-B needs to get used
+- An OSP must integrate and use the GAIA-X Digital Clearing House to validate e. g., the Legal Person Self-Description.
+- An OSP CAN offer a wallet solution for their customers; if not offered, the wallet of the connected CSP-B needs to get used
 
 <br>
 
-&uarr; [zurück zur Übersicht](#top)
+&uarr; [back to top](#top)
 
 <br>
 <br>
@@ -54,24 +54,24 @@ The OSP certification details are stored on the catena-x homepage. Please follow
 After receiving the OSP certification; the company needs to register with each CSB-x to which they wanna connect.
 2 Options are possible:
 
-a) register as OSP as part of the registration process [Link](/docs/user/01.%20Onboarding/02.%20Registration/04.%20Company%20Role%20%26%20Consent.md)  
-b) receive the OSP role after the initial registration [Link](/docs/user/02.%20Technical%20Integration/05.%20Company%20Role/Change%20Company%20Role.md)
+a) register as OSP as part of the registration process: [Company Role & Consent](/docs/user/01.%20Onboarding/02.%20Registration/04.%20Company%20Role%20%26%20Consent.md)  
+b) receive the OSP role after the initial registration: [Change Company Role](/docs/user/02.%20Technical%20Integration/05.%20Company%20Role/Change%20Company%20Role.md)
 
 <br>
 
-&uarr; [zurück zur Übersicht](#top)
+&uarr; [back to top](#top)
 
 <br>
 <br>
 
 ### Register your (OSP) customer IdP
 
 Before running any registrations, the IdP used for the customer accounts need to get registered.
-This can be done my creating an IdP connection managed [Link](/docs/user/02.%20Technical%20Integration/02.%20Identity%20Provider%20Management/02.%20Configure%20Company%20IdP.md)
+This can be done by creating an IdP connection: [Configure Company IdP](/docs/user/02.%20Technical%20Integration/02.%20Identity%20Provider%20Management/02.%20Configure%20Company%20IdP.md)
 
 <br>
 
-&uarr; [zurück zur Übersicht](#top)
+&uarr; [back to top](#top)
 
 <br>
 <br>
@@ -84,7 +84,7 @@ Therefor the OSP must integrate their registration component with the CSP-B/A in
 
 <br>
 
-&uarr; [zurück zur Übersicht](#top)
+&uarr; [back to top](#top)
 
 <br>
 <br>
@@ -94,11 +94,11 @@ Therefor the OSP must integrate their registration component with the CSP-B/A in
 To provide the OSP an status update for the customer registration and support possible customer interactions in case of problems or missing progress; the status callback can be used.
 The connect to the registration status callback; the OSP needs to implement an interface and register the interface endpoint on the CSP side.
 
-Detailes can get found here: [Link](/docs/developer/01.%20Registration/03.%20Registration%20External/02.%20OSP%20Registration%20Callback.md)
+Details can be found here: [OSP Registration Callback](/docs/developer/01.%20Registration/03.%20Registration%20External/02.%20OSP%20Registration%20Callback.md)
 
 <br>
 
-&uarr; [zurück zur Übersicht](#top)
+&uarr; [back to top](#top)
 
 <br>
 <br>
@@ -108,12 +108,11 @@ Detailes can get found here: [Link](/docs/developer/01.%20Registration/03.%20Reg
 _under implementation_
 <br>
 
-&uarr; [zurück zur Übersicht](#top)
+&uarr; [back to top](#top)
 
 <br>
 <br>
 
-
 ## NOTICE
 
 This work is licensed under the [Apache-2.0](https://www.apache.org/licenses/LICENSE-2.0).

diff --git a/...eveloper/01. Registration/01. Registration Process/02. Registration External.md b/...eveloper/01. Registration/01. Registration Process/02. Registration External.md
@@ -7,7 +7,7 @@ This registration method allows users to register through a partnership with an
 
 ### Workflow
 
-1. **User Chooses External Partner**: Outside of the operator portal, the user selects an onbaording provider (e.g. a platform which is OSP of CX and where the company is already successfully registered)
+1. **User Chooses External Partner**: Outside of the operator portal, the user selects an onboarding provider (e.g. a platform which is OSP of CX and where the company is already successfully registered)
 2. **Select the option to get registered at CX**: The user selects at the external provider side to register for the CX dataspace.
 3. **API Registration**: Upon selection, the partner system calls the operator application's API endpoint with the company/user's data.
 4. **Registration Creation**: The operator validates the data and creates a new account.
@@ -72,7 +72,6 @@ With the registration invite, following activities are triggered and automatical
 <br>
 <br>
 
-
 #### Registration Creation
 
 The registration request validation runs through the same validation and process steps as implemented for "internal" registrations.
@@ -88,6 +87,7 @@ _documentation to be added_
 <br>
 
 #### Registration Validation and Approval
+
 The operator validates the registration and runs through the approval process till activation.
 
 [Approval Validation Process](/docs/developer/01.%20Registration/04.%20Registration%20Approval/03.%20Registration%20Approval%20Process.md)