Rephrased

docs/odata-protocol/odata-protocol.html

@@ -984,7 +984,7 @@ <h2 id="103-entity"><a name="Entity" href="#Entity">10.3 Entity</a></h2>
 <p>Context URL template:</p>
 <pre><code>{context-url}#{entity-set}/$entity
 {context-url}#{type-name}</code></pre>
-<p>If a response or response part is a single entity of the declared type of an entity set, its name with <code>/$entity</code> appended is the context URL fragment.</p>
+<p>If a response or response part is a single entity of the declared type of an entity set, the context URL fragment is the entity set’s name with <code>/$entity</code> appended.</p>
 <div class="example">
 <p>Example 13: resource URL and corresponding context URL</p>
 <pre><code>http://host/service/Customers(1)

docs/odata-protocol/odata-protocol.md

@@ -2061,8 +2061,8 @@ Context URL template:
     {context-url}#{type-name}
 
 If a response or response part is a single entity of the declared type
-of an entity set, its
-name with `/$entity` appended is the context URL fragment.
+of an entity set, the context URL fragment is the entity set's
+name with `/$entity` appended.
 
 ::: example
 Example 13: resource URL and corresponding context URL

odata-protocol/10 Context URL.md

@@ -105,8 +105,8 @@ Context URL template:
     {context-url}#{type-name}
 
 If a response or response part is a single entity of the declared type
-of an entity set, its
-name with `/$entity` appended is the context URL fragment.
+of an entity set, the context URL fragment is the entity set's
+name with `/$entity` appended.
 
 ::: example
 Example ##ex: resource URL and corresponding context URL