Last-minute changes

docs/odata-protocol/odata-protocol.html

@@ -1360,7 +1360,7 @@ <h2 id="103-entity"><a id="Entity" href="#Entity">10.3 Entity</a></h2>
 <pre><code>http://host/service/Orders(4711)/Items(1)
 http://host/service/$metadata#Orders(4711)/Items/$entity</code></pre>
 </div>
-<p>If the entity is within a collection, but a canonical collection cannot be determined, such as for an entity returned from a function or action with no entity set path, a function import or action import with no specified entity set, or a navigation property with no navigation property binding, the context URL fragment specifies the type <code>{type-name}</code> of the returned entity.</p>
+<p>If the entity is within a collection, but a canonical collection cannot be determined, such as for an entity returned from a function or action with no entity set path, a function import or action import with no specified entity set, or a navigation property with no navigation property binding, the context URL fragment specifies the <code>{type-name}</code> of the returned entity.</p>
 </details>
 <details open><summary>
 <h2 id="104-singleton"><a id="Singleton" href="#Singleton">10.4 Singleton</a></h2>
@@ -1511,7 +1511,7 @@ <h2 id="1012-entity-reference"><a id="EntityReference" href="#EntityReference">1
 </summary>
 <p>Context URL template:</p>
 <pre><code>{context-url}#$ref</code></pre>
-<p>If a response is one entity reference, <code>$ref</code> is the context URL fragment.</p>
+<p>If a response is a single entity reference, <code>$ref</code> is the context URL fragment.</p>
 <div class="example">
 <p>Example 27: resource URL and corresponding context URL for a single entity reference</p>
 <pre><code>http://host/service/Orders(10643)/Customer/$ref

docs/odata-protocol/odata-protocol.md

@@ -2115,7 +2115,7 @@ cannot be determined, such as for an entity
 returned from a function or action with no entity set path, a function
 import or action import with no specified entity set, or a navigation
 property with no navigation property binding, the context URL fragment specifies
-the type `{type-name}` of the returned entity.
+the `{type-name}` of the returned entity.
 
 ## <a id="Singleton" href="#Singleton">10.4 Singleton</a>
 
@@ -2418,7 +2418,7 @@ Context URL template:
 
     {context-url}#$ref
 
-If a response is one entity reference, `$ref` is the context URL
+If a response is a single entity reference, `$ref` is the context URL
 fragment.
 
 ::: example

odata-protocol/10 Context URL.md

@@ -138,7 +138,7 @@ cannot be determined, such as for an entity
 returned from a function or action with no entity set path, a function
 import or action import with no specified entity set, or a navigation
 property with no navigation property binding, the context URL fragment specifies
-the type `{type-name}` of the returned entity.
+the `{type-name}` of the returned entity.
 
 ## ##subsec Singleton
 
@@ -441,7 +441,7 @@ Context URL template:
 
     {context-url}#$ref
 
-If a response is one entity reference, `$ref` is the context URL
+If a response is a single entity reference, `$ref` is the context URL
 fragment.
 
 ::: example