Rephrased

docs/odata-json-format/odata-json-format.html

@@ -1662,7 +1662,7 @@ <h1 id="17-bound-action"><a name="BoundAction" href="#BoundAction">17 Bound Acti
 <h1 id="18-action-invocation"><a name="ActionInvocation" href="#ActionInvocation">18 Action Invocation</a></h1>
 <p>Action parameter values are encoded in a single JSON object in the request body.</p>
 <p>Each non-binding parameter value is encoded as a separate name/value pair in this JSON object. The name is the name of the parameter. The value is the parameter value in the JSON representation appropriate for its type. Entity typed parameter values MAY include a subset of the properties, or just the <a href="#EntityReference">entity reference</a>, as appropriate to the action. Stream typed parameter values are represented following the same rules as inlined <a href="#StreamProperty">stream properties</a>.</p>
-<p>Alternatively, values of non-binding parameters MAY be specified as common expressions <a href="#ODataURL">OData-URL, section 5.1.1</a>. In the case of a bound action these MAY contain path expressions <a href="#ODataURL">OData-URL, section 5.1.1.15</a>, which the service evaluates on the binding parameter value. Such parameters are encoded as name/value pairs where the name is the name of the parameter followed by <code>@expressionUrl</code> and the value is the common expression. As the following example demonstrates, even non-transient entities can be passed as non-binding action parameters in this way.</p>
+<p>Alternatively, values of non-binding parameters MAY be specified as common expressions <a href="#ODataURL">OData-URL, section 5.1.1</a>. In the case of a bound action these MAY contain path expressions <a href="#ODataURL">OData-URL, section 5.1.1.15</a>, which the service evaluates on the binding parameter value. Such parameters are encoded as name/value pairs where the name is the name of the parameter followed by <code>@expressionUrl</code> and the value is the common expression. As the following example demonstrates, non-transient entities can be passed as non-binding action parameters through a resource path in this way.</p>
 <div class="example">
 <p>Example 49: An employee requests leave from their manager for the next two weeks:</p>
 <div class="sourceCode" id="cb53"><pre class="sourceCode json"><code class="sourceCode json"><span id="cb53-1"><a href="#cb53-1" aria-hidden="true" tabindex="-1"></a><span class="er">POST</span> <span class="er">/service/Employees(23)/self.RequestLeave</span></span>

docs/odata-json-format/odata-json-format.md

@@ -2978,8 +2978,9 @@ Alternatively, values of non-binding parameters MAY be specified as common expre
 these MAY contain path expressions [OData-URL, section 5.1.1.15](#ODataURL), which
 the service evaluates on the binding parameter value. Such parameters are encoded as name/value
 pairs where the name is the name of the parameter followed by `@expressionUrl` and
-the value is the common expression. As the following example demonstrates, even
-non-transient entities can be passed as non-binding action parameters in this way.
+the value is the common expression. As the following example demonstrates,
+non-transient entities can be passed as non-binding action parameters through a
+resource path in this way.
 
 ::: example
 Example 49: An employee requests leave from their manager for the next two weeks:

odata-json-format/16 Bound Function.md

@@ -239,8 +239,9 @@ Alternatively, values of non-binding parameters MAY be specified as common expre
 these MAY contain path expressions [OData-URL, section 5.1.1.15](#ODataURL), which
 the service evaluates on the binding parameter value. Such parameters are encoded as name/value
 pairs where the name is the name of the parameter followed by `@expressionUrl` and
-the value is the common expression. As the following example demonstrates, even
-non-transient entities can be passed as non-binding action parameters in this way.
+the value is the common expression. As the following example demonstrates,
+non-transient entities can be passed as non-binding action parameters through a
+resource path in this way.
 
 ::: example
 Example ##ex: An employee requests leave from their manager for the next two weeks: