@ralfhandl's suggestion

docs/odata-protocol/odata-protocol.html

@@ -2410,7 +2410,7 @@ <h4 id="11431-update-related-entities-when-updating-an-entity"><a id="UpdateRela
 </summary>
 <p>Update requests with an OData-Version header with a value of <code>4.0</code> MUST NOT contain related entities as inline content. Such requests MAY contain binding information for navigation properties. For single-valued navigation properties this replaces the relationship. For collection-valued navigation properties this adds to the relationship.</p>
 <p>Payloads with an <code>OData-Version</code> header with a value of <code>4.01</code> or greater MAY include nested entities and entity references that specify the full set of to be related entities, or a nested <a href="#DeltaPayloads">delta payload</a> representing the related entities that have been added, removed, or changed. Such a request is referred to as a “deep update”. If the nested collection is represented identical to an expanded navigation property, then the set of nested entities and entity references specified in a successful update request represents the full set of entities to be related according to that relationship and MUST NOT include added links, deleted links, or deleted entities.</p>
-<p>If a navigation property is absent from a <code>PUT</code> or <code>PATCH</code> request payload, the referenced or contained entity, or the collection thereof, which the navigation property targets remain unchanged by a successful update.</p>
+<p>If a navigation property is absent from a <code>PUT</code> or <code>PATCH</code> request payload, the referenced or contained entity, or the collection thereof, remain unchanged by a successful update.</p>
 <div class="example">
 <p>Example 78: using the JSON format, a 4.01 <code>PATCH</code> request can update a manager entity. Following the update, the manager has three direct reports; two existing employees and one new employee named <code>Suzanne Brown</code>. The <code>LastName</code> of employee 6 is updated to <code>Smith</code>.</p>
 <div class="sourceCode" id="cb97"><pre class="sourceCode json"><code class="sourceCode json"><span id="cb97-1"><a href="#cb97-1" aria-hidden="true" tabindex="-1"></a><span class="fu">{</span></span>

docs/odata-protocol/odata-protocol.md

@@ -4454,8 +4454,7 @@ set of entities to be related according to that relationship and MUST
 NOT include added links, deleted links, or deleted entities.
 
 If a navigation property is absent from a `PUT` or `PATCH` request payload, the referenced
-or contained entity, or the collection thereof, which the navigation property targets
-remain unchanged by a successful update.
+or contained entity, or the collection thereof, remain unchanged by a successful update.
 
 ::: example
 Example 78: using the JSON format, a 4.01 `PATCH` request can update a

odata-protocol/11.4 Data Modification.md

@@ -450,8 +450,7 @@ set of entities to be related according to that relationship and MUST
 NOT include added links, deleted links, or deleted entities.
 
 If a navigation property is absent from a `PUT` or `PATCH` request payload, the referenced
-or contained entity, or the collection thereof, which the navigation property targets
-remain unchanged by a successful update.
+or contained entity, or the collection thereof, remain unchanged by a successful update.
 
 ::: example
 Example ##ex: using the JSON format, a 4.01 `PATCH` request can update a