Grammar/style updates

Author: keharper

src/pages/webhooks/responses.md

@@ -7,7 +7,7 @@ keywords:
 
 # Webhook responses and logging
 
-Currently, Adobe Commerce webhooks only support responses in JSON format. The response may be a single operation or the array of operations which will be executed consequently.
+Currently, Adobe Commerce webhooks support responses in JSON format only. The response may be a single operation or an array of operations to be executed afterward.
 Each operation must contain some required fields based on the desired operation.
 
 Exceptions and notices are logged in the `<installation_directory>/var/log/system.log` file.
@@ -16,19 +16,19 @@ Exceptions and notices are logged in the `<installation_directory>/var/log/syste
 
 The endpoint is expected to return a `200` response and a JSON object or array of objects that indicates the result of the operation. Each operation object can contain the list of fields based on the operation (`op`) which should be performed.
 
-At the moment Adobe Commerce webhooks support 5 different operations:
+Adobe Commerce webhooks support the following operations:
 
-operation | Description
+Operation | Description
 --- | ---
-`success` | the process that triggered the original event continues without any changes.
-`exception` | causes Commerce to terminate the process that triggered the original event
-`add` | updates the arguments in the original events by adding data described in the operation
-`replace` | replaces the arguments values in the original events based based on the response
-`remove` | removes values or nodes from the arguments in the original event by provided path
+`success` | The process that triggered the original event continues without any changes.
+`exception` | Causes Commerce to terminate the process that triggered the original event.
+`add` | Updates the arguments in the original event by adding data described in the operation
+`replace` | Replaces argument values in the original event, based on the response.
+`remove` | Removes values or nodes from the arguments in the original event by the provided path
 
 ### Success operation
 
-The `success` operation is returned in cases when changes are not needed and the process that triggered the original event continues without any changes.
+The `success` operation is returned when changes are not needed. The process that triggered the original event continues without any changes.
 
 The response of a successful request is as follows:
 
@@ -44,32 +44,32 @@ The `exception` operation causes Commerce to terminate the process that triggere
 
 Field | Type | Description
 --- | --- | ---
-`op` | required | `exception`
-`class` | optional | specifies the exception class. If `class` is not set, the `\Magento\Framework\Exception\LocalizedException` will be thrown.
-`message` | optional |  specifies the exception message. If this field is not explicitly set, then the message defined in the `fallbackErrorMessage` configuration field will be returned. If `fallbackErrorMessage` is not set, the system default error message will be shown.
+`op` | Required | Contains `exception`.
+`class` | Optional | Specifies the exception class. If `class` is not set, `\Magento\Framework\Exception\LocalizedException` will be thrown.
+`message` | Optional | Specifies the exception message. If this field is not explicitly set, then the message defined in the `fallbackErrorMessage` configuration field will be returned. If `fallbackErrorMessage` is not set, the system default error message will be returned.
 
 If an error occurs, the response is similar to the following:
 
 ```json
 {
   "op": "exception",
   "class": "Path\\To\\Exception\\Class",
-  "message": "The product can not be added to the cart as it is out of the stock"
+  "message": "The product cannot be added to the cart because it is out of the stock"
 }
 ```
 
 ### Add operation
 
-The `add` operation causes Commerce to add provided `value` to the provided `path` to the triggered event arguments
+The `add` operation causes Commerce to add the provided `value` to the provided `path` to the triggered event arguments
 
 Field | Type     | Description
 --- |----------| ---
-`op` | required | `add`
-`path` | required | specifies the path at which the `value` should be added to the triggered event arguments
-`value` | required | specifies the value that should be added, can be as a single value or in the array format
-`instance` | optional | specifies the DataObject class name which should be created based on `value` and added to the provided `path`. Used for the cases when the object should be added in provided path.
+`op` | Required | Contains `add`.
+`path` | Required | Specifies the path at which the `value` should be added to the triggered event arguments.
+`value` | Required | Specifies the value to be added. This can be as a single value or in an array format.
+`instance` | Optional | Specifies the `DataObject` class name to create, based on the  `value` and added to the provided `path`. Use this field for cases when the object should be added in provided path.
 
-For example, we want to add a new shipping method to the triggered event result payload:
+For example, we want to add a new shipping method to the triggered event result payload.
 The result is an array of `Magento\Quote\Model\Cart\ShippingMethod` objects:
 
 ```php
@@ -97,7 +97,7 @@ To add a new shipping method to that result, the response from the webhook would
 }
 ```
 
-Based on this operation the new instance of `Magento\Quote\Model\Cart\ShippingMethodInterface` will be created and added to the result array of shipping methods.
+Based on this operation, the new instance of `Magento\Quote\Model\Cart\ShippingMethodInterface` will be created and added to the result array of shipping methods.
 
 ```php
 $result = [
@@ -109,16 +109,16 @@ $result = [
 
 ### Replace operation
 
-The `replaces` operation causes Commerce to replace a value in triggered event arguments for the provided `path`
+The `replace` operation causes Commerce to replace a value in triggered event arguments for the provided `path`
 
 Field | Type     | Description
 --- |----------| ---
-`op` | required | `replace`
-`path` | required | specifies the path at which the value should be replaced with the provided `value`
-`value` | required | specifies the new value that replaces the value by provided `path`, can be as a single or in the array format
-`instance` | optional | specifies the DataObject class name which should be created based on `value` and used as value to replaced by path `path`.
+`op` | Required | Contains `replace`.
+`path` | Required | Specifies the path at which the value should be replaced with the provided `value`.
+`value` | Required | Specifies the replacement value. This can be as a single value or in an array format.
+`instance` | Optional | Specifies the `DataObject` class name to create, based on the  `value` and added to the provided `path`.
 
-For example, we want to a replace a nested element in the triggered event result payload:
+The following example replaces a nested element in the triggered event result payload:
 
 ```php
 $result = [
@@ -158,10 +158,10 @@ The `remove` operation causes Commerce to remove a value or node in triggered ev
 
 Field | Type     | Description
 --- |----------| ---
-`op` | required | `remove`
-`path` | required | specifies the path at which the value should be removed
+`op` | Required | Contains `remove`.
+`path` | Required | Specifies the path at which the value should be removed.
 
-For example, we want to a remove en element `key2` from the triggered event result payload:
+The following example removes element `key2` from the triggered event result payload:
 
 ```php
 $result = [