From 9df4f27a9e932409269c9a19c67bec0e06ce7cee Mon Sep 17 00:00:00 2001
From: Ekaterina Mitova <ekaterina.mitova@sap.com>
Date: Sun, 29 Oct 2023 01:22:54 +0300
Subject: [PATCH] Update install-mock-server-cf.md

Language review and consistency.
---
 .../deploy/cf/install-mock-server-cf.md       | 30 +++++++++++--------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/documentation/eventing/deploy/cf/install-mock-server-cf.md b/documentation/eventing/deploy/cf/install-mock-server-cf.md
index 0c15044..c428534 100644
--- a/documentation/eventing/deploy/cf/install-mock-server-cf.md
+++ b/documentation/eventing/deploy/cf/install-mock-server-cf.md
@@ -1,24 +1,28 @@
-# Option 1 - Install Mock Server in SAP BTP Cloud Foundry Runtime
+# Option 1 - Deploy a Mock Server in SAP BTP, Cloud Foundry Runtime
 
-## Pre requisite
-The Remote Service Integration tutorial was executed and mock server was deployed on CF and destination was created following steps [here](../../../remote-service/install-mock-server/install-mock-server-cf.md)
+## Prerequisite
+* You have completed the Remote Service Integration tutorial.
+* You have deployed a mock server in the SAP BTP, Cloud Foundry runtime.
+* You have created a destination using the following steps [here](../../../remote-service/install-mock-server/install-mock-server-cf.md).
 
-## Re-Deploy the Mock Server Application
+## Redeploy the Mock Server Application
+
+In this section you would redeploy the mock server and bind it to the Event Mesh instance so that the mock server can send events. 
 
-In this section you would redeploy the mock server and bind it to Event Mesh instance so that mock server can emit events. 
 1. In the menu, choose **File** and then choose **Open Folder** from the dropdown menu.
 
 2. To open the mock server project, choose **projects** &rarr; **cloud-extension-ecc-business-process** and then choose **Open**.
 
-3. In the project folder, open **mta.yaml** file
+3. In the project folder, open the **mta.yaml** file:
 
-    - add the below code snippet to the **resources** section
+    1. Add the following code snippet to the `resources` section:
+       
         ```yaml
         - name: inicdent-management-messaging
           type: org.cloudfoundry.existing-service
         ```
 
-    - Adds the below entry in the `requires` section of `mock-srv` module
+    2. Adds the following entry in the `requires` section of the `mock-srv` module:
 
         ```yaml
             - name: inicdent-management-messaging
@@ -29,15 +33,17 @@ In this section you would redeploy the mock server and bind it to Event Mesh ins
 5. When the project is built successfully, you will see a new **mta_archives** folder in your project with the **Mockserver_1.0.0.mtar** file inside. Right-click that file and choose **Deploy MTA Archive**.
 
 ## Deploy the Incident Management Application
+
 1. In the menu, choose **File** and then choose **Open Folder** from the dropdown menu.
-1. To open the Incident Managemnt project, choose **projects** &rarr; **incident-nanagement** and then choose **Open**.
-2. Navigate to package.json and change credentials to 
+2. To open the Incident Management project, choose **projects** &rarr; **incident-nanagement** and then choose **Open**.
+3. Navigate to the **package.json** file and change the credentials to:
+   
     ```json
     "credentials": {
             "destination": "<destination_name>",
             "path": "/v2/odata/v4/api-business-partner"
           }
     ```
-**Note** - As **destination_name** you must enter the name of the destination created while installing mock server to SAP BTP Cloud Foundry Runtime.
+>Note: Replase **destination_name** with the name of the destination you have created when installing mock server in the SAP BTP, Cloud Foundry Runtime.
 
-2. Follow the steps in the [Deploy to Cloud Foundry tutorial](./deploy-to-cf.md).
+2. Follow the steps in the [Deploy to Cloud Foundry](./deploy-to-cf.md) tutorial.