Reference the example

docs/odata-protocol/odata-protocol.html

@@ -2894,7 +2894,7 @@ <h4 id="11551-invoking-an-action"><a name="InvokinganAction" href="#InvokinganAc
 <span id="cb119-10"><a href="#cb119-10" aria-hidden="true" tabindex="-1"></a>  <span class="dt">&quot;discountCode&quot;</span><span class="fu">:</span> <span class="st">&quot;BLACKFRIDAY&quot;</span></span>
 <span id="cb119-11"><a href="#cb119-11" aria-hidden="true" tabindex="-1"></a><span class="fu">}</span></span></code></pre></div>
 </div>
-<p>Clients MAY associate an id with individual values nested in a parameter value in the request payload by using the <a href="https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#ContentID"><code>Core.ContentID</code></a> term defined in <a href="#ODataVocCore">OData-VocCore</a>. Services that respond with <a href="#ResponseCode200OK"><code>200 OK</code></a> SHOULD annotate corresponding entities in the response using the same <a href="https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#ContentID"><code>Core.ContentID</code></a> value as specified in the request. See the example in <a href="#ODataJSON">OData-JSON, section 19.4</a>.</p>
+<p>Clients MAY associate an id with individual values nested in a parameter value in the request payload by using the <a href="https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#ContentID"><code>Core.ContentID</code></a> term defined in <a href="#ODataVocCore">OData-VocCore</a>. Services that respond with <a href="#ResponseCode200OK"><code>200 OK</code></a> SHOULD annotate corresponding entities in the response using the same <a href="https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#ContentID"><code>Core.ContentID</code></a> value as specified in the request. See the “sales quotation to order” example in <a href="#ODataJSON">OData-JSON, section 19.4</a>.</p>
 </details>
 <details open><summary>
 <h4 id="11552-action-overload-resolution"><a name="ActionOverloadResolution" href="#ActionOverloadResolution">11.5.5.2 Action Overload Resolution</a></h4>

docs/odata-protocol/odata-protocol.md

@@ -5740,7 +5740,7 @@ term defined in [OData-VocCore](#ODataVocCore).
 Services that respond with [`200 OK`](#ResponseCode200OK) SHOULD annotate corresponding
 entities in the response using the same
 [`Core.ContentID`](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#ContentID)
-value as specified in the request. See the example in [OData-JSON, section 19.4](#ODataJSON).
+value as specified in the request. See the "sales quotation to order" example in [OData-JSON, section 19.4](#ODataJSON).
 
 #### <a name="ActionOverloadResolution" href="#ActionOverloadResolution">11.5.5.2 Action Overload Resolution</a>
 

odata-protocol/11.5 Operations.md

@@ -471,7 +471,7 @@ term defined in [OData-VocCore](#ODataVocCore).
 Services that respond with [`200 OK`](#ResponseCode200OK) SHOULD annotate corresponding
 entities in the response using the same
 [`Core.ContentID`](https://github.com/oasis-tcs/odata-vocabularies/blob/main/vocabularies/Org.OData.Core.V1.md#ContentID)
-value as specified in the request. See the example in [OData-JSON, section 19.4](#ODataJSON).
+value as specified in the request. See the "sales quotation to order" example in [OData-JSON, section 19.4](#ODataJSON).
 
 #### ##subsubsubsec Action Overload Resolution