SD-2837-updated iss and surr prompts

ebl-issuance/src/main/resources/standards/eblissuance/instructions/prompt-iss-reqres-ebltype.md

@@ -1,9 +1,17 @@
-Send an issuance request for an eBL of type EBL_TYPE that has not yet been issued to get response code
-RESPONSE_CODE.
+Send an issuance request for an eBL of type **EBL_TYPE** to the platform that has not yet been issued to get response
+code **RESPONSE_CODE**.
 
-Process an automatic response from the platform.
+### What Happens:
 
-Press "Refresh status" to refresh the scenario status and conformance checks.
+1. **Your carrier sends**: PUT request to `/ebl-issuance-requests` with the issuance request details
+2. **Synthetic platform responds**: Automatically sends an issuance response by making a POST request to
+   `/ebl-issuance-responses` with response code **RESPONSE_CODE**
+3. **Conformance validates**: Your carrier's request conforms to the DCSA eBL Issuance API standard
+4. **Your Carrier**: Process the automatic response from the synthetic platform
 
-Press "Action completed" to mark this scenario action completed.
+### Next Steps:
+
+Press **"Refresh status"** to update the scenario status and view conformance check results.
+
+Press **"Action completed"** when you have sent the request and received the response.
 

ebl-issuance/src/main/resources/standards/eblissuance/instructions/prompt-platform-psp.md

@@ -27,7 +27,7 @@ PUBLIC_KEY
 ### 2. Scenario Parameters
 
 Supply the following parameters so that when your platform system receives the issuance request, it sends back an
-asynchronous response with the code **RESPONSE_CODE**.
+asynchronous response by making a POST request to `/ebl-issuance-responses` with the code **RESPONSE_CODE**.
 
 These parameters customize the requests sent to your platform application throughout the scenario.
 
@@ -65,4 +65,4 @@ These parameters customize the requests sent to your platform application throug
 - `issuingPartyPartyCode` - Copied into the first element of the `identifyingCodes` array in
   `/documentParties/issuingParty` object as the value of `partyCode`
 - `issuingPartyCodeListName` - Copied into the first element of the `identifyingCodes` array in
-  `/documentParties/issuingParty` object as the value of `codeListName`
+  `/documentParties/issuingParty` object as the value of `codeListName`

ebl-surrender/src/main/resources/standards/eblsurrender/instructions/prompt-surrender-reqres.md

@@ -3,7 +3,8 @@ Send a surrender request for **SURRENDER_TYPE** from your platform to the synthe
 ### What Happens:
 
 1. **Your platform sends**: POST request to `/ebl-surrender-requests` with the surrender request details
-2. **Synthetic carrier responds**: Automatically accepts or rejects the surrender request
+2. **Synthetic carrier responds**: Automatically accepts or rejects the surrender request by making a POST request to
+   `/ebl-surrender-responses`.
 3. **Conformance validates**: Your platform's request conforms to the DCSA eBL Surrender API standard
 
 ### Next Steps:

ebl-surrender/src/main/resources/standards/eblsurrender/instructions/prompt-surrender-ssp.md

@@ -9,7 +9,8 @@ Please provide the required information for a **EBL_TYPE** that your system can
 ### What Happens Next:
 
 1. The conformance platform will send a surrender request to your carrier system
-2. Your system should automatically **RESPONSE** the surrender request
+2. Your system should automatically **RESPONSE** the surrender request by making a POST request to
+   `/ebl-surrender-responses`
 3. The platform will validate your response against the DCSA eBL Surrender API standard
 
-**Note:** If you do not send a response, the conformance report will show "❔" (missing traffic) for the response checks.
+**Note:** If you do not send a response, the conformance report will show "❔" (missing traffic) for the response checks.