Did some language clean up / clarification.

Simon Prickett · web-flow · commit fbb54ac46b86 · 2023-08-01T15:51:02.000+01:00
diff --git a/docs/commands/json.merge.md b/docs/commands/json.merge.md
@@ -1,43 +1,43 @@
 Merge a given JSON value into matching paths. Consequently, JSON values at matching paths are updated, deleted, or expanded with new children.
 
-This command complies with [RFC7396](https://datatracker.ietf.org/doc/html/rfc7396) Json Merge Patch
+This command complies with [RFC7396](https://datatracker.ietf.org/doc/html/rfc7396) JSON Merge Patch
 
 [Examples](#examples)
 
 ## Required arguments
 
 <details open><summary><code>key</code></summary>
 
-is key to merge into.
+is the key to merge into.
 </details>
 
 <details open><summary><code>path</code></summary>
 
-is JSONPath to specify. For non-existing keys the `path` must be `$`. For existing keys, for each matched `path`, the value that matches the `path` is being merged with the JSON `value`. For existing keys, when the path exists, except for the last element, a new child is added with the JSON `value`.
+is the JSONPath to specify where in the JSON document to apply the merge. For non-existing keys the `path` must be `$`. For existing keys, for each matched `path`, the value that matches the `path` is merged with the JSON `value`. For existing keys, when the path exists, except for the last element, a new child is added with the JSON `value`.
 
 </details>
 
 <details open><summary><code>value</code></summary>
 
-is JSON value to merge with at the specified path. Merging is done according to the following rules per JSON value in the `value` argument while considering the corresponding original value if it exists:
+is the JSON value to merge with at the specified path. Merging is done according to the following rules per JSON value in the `value` argument while considering the corresponding original value if it exists:
 *   merging an existing object key with a `null` value deletes the key
 *   merging an existing object key with non-null value updates the value
-*   merging a non-existing object key adds the key and value
-*   merging an existing array with any merged value, replaces the entire array with the value
+*   merging a nonexistent object key adds the key and value
+*   merging an existing array with any merged value replaces the entire array with the value
 </details>
 
 ## Return value
 
-JSET.MERGE returns a simple string reply: `OK` if executed correctly or `error` if fails to set the new values
+JSET.MERGE returns a simple string reply: `OK` if executed correctly or `error` if fails to set the new values.
 
 For more information about replies, see [Redis serialization protocol specification](/docs/reference/protocol-spec).
 
 ## Examples
 
-The JSON.MERGE provide four different behaviours to merge changes on a given key: create unexistent path, update an existing path with a new value, delete a existing path or replace an array with a new array
+The JSON.MERGE command provides four different behaviors to merge changes on a given key: create a new path, update an existing path with a new value, delete a existing path or replace an array with a new array.
 
 <details open>
-<summary><b>Create a unexistent path-value</b></summary>
+<summary><b>Create a new path-value</b></summary>
 
 {{< highlight bash >}}
 redis> JSON.SET doc $ '{"a":2}'
