CrossBorder-Gateway/Domibus/Server-setup-guide.md

@@ -23,7 +23,7 @@ The instructions in these guidelines use variables that must be replaced with th
 - **`{DOMIBUS_ACCESS_POINT}`**: This is the designated name for your Domibus instance. Choose a clear and descriptive name, such as `france_ap`.
 - **`{CENTRAL_HOSTNAME}`**: Denotes the public IP address/hostname of the central Domibus server.
 - **`{CENTRAL_PORT}`**: Represents the internet-accessible port of the central Domibus server.
-- **`{CENTRAL_ACCESS_POINT}`**: This serves as the designated identifier for the central Domibus access point. It may be commonly referred to as `europe_ap` in some screenshots, however, please note that this is not the actual access point name, as we refrain from sharing sensitive information on this wiki
+- **`{CENTRAL_ACCESS_POINT}`**: This serves as the designated identifier for the central Domibus access point. It may be commonly referred to as `europe_ap` in some screenshots, however, please note that this is not the actual access point name, as we refrain from sharing sensitive information on this wiki.
 - **`{KEYSTORE_PASSWORD}`**: Refers to the password for your Java KeyStore.
 - **`{PRIVATE_KEY_PASSWORD}`**: Refers to the password for the private key within your Java KeyStore.
 - **`{TRUSTSTORE_PASSWORD}`**: Refers to the password for your Java TrustStore.
@@ -350,7 +350,7 @@ http://{CENTRAL_HOSTNAME}:{CENTRAL_PORT}/domibus/services/msh
 Import the central certificate
 
 
-Navigate to the `Identifiers` section, then select `+ New`. Assign the value of `PartyId` as **`{CENTRAL_ACCESS_POINT}`**, ensuring to configure the following properties accordingly:
+Navigate to the `Identifiers` section, then select `+ New`. Assign the value of `Party Id` as **`{CENTRAL_ACCESS_POINT}`**, ensuring to configure the following properties accordingly:
 
 ```
 Party Id Type: partyTypeUrn
@@ -369,20 +369,20 @@ Verify on the `Parties` tab to ensure that all parties are configured correctly.
 # Testing Configuration
 Congratulations on successfully setting up your Domibus server! Now, for testing, you have two options:
 
-- Console Monitoring Tests: Essential for validating basic functionality, specifically to ensure the connection status between your access point and any additional access points added in the pmode. This test focuses on assessing the integrity of the connection.
+- **Console Monitoring Test:** Essential for validating basic functionality, specifically to ensure the connection status between your access point and any additional access points added in the pmode. This test focuses on assessing the integrity of the connection.
 
-SoapUI Test: For a deeper understanding of message exchange, you can perform this advanced test. It's entirely optional and recommended for those seeking a more comprehensive validation.
+- **SoapUI Test:** For a deeper understanding of message exchange, you can perform this advanced test. It's entirely optional and recommended for those seeking a more comprehensive validation.
 
 Feel free to choose the testing approach that suits your needs or test both. 
 
 ### 1 - Console Monitoring test
 :computer:
 
-In the Domibus Console, navigate to the `Connection Monitoring` section and try sending a message to your own Access Point and to **`{CENTRAL_ACCESS_POINT}`**. If the status shows as green for both, your Domibus server is ready for message exchange.
+In the Domibus Console, navigate to the `Connection Monitoring` section and try sending a message to your own access point and to **`{CENTRAL_ACCESS_POINT}`**. If the status shows as green for both, your Domibus server is ready for message exchange.
 
 ![monitoring](/img/domibus/image6.png)
 
-### 2- SoapUI test
+### 2- SoapUI test (Optional)
 :computer:
 
 To perform testing with SoapUI, follow these steps on your personal computer: