Punctuation on the wrong side of the backtick

docs/odata-csdl-json/odata-csdl-json.html

@@ -3011,7 +3011,7 @@ <h4 id="14441-canonical-functions"><a name="CanonicalFunctions" href="#Canonical
 </div>
 <p><code>ProductName</code> is of type <code>String</code>, <code>Quantity</code> in complex type <code>Available</code> is of type <code>Decimal</code>, and <code>Unit</code> in <code>Available</code> is of type enumeration, so the result of the <code>Path</code> expression is represented as the member name of the enumeration value.</p>
 <h4 id="14442-function-odatafilluritemplate"><a name="FunctionodatafillUriTemplate" href="#FunctionodatafillUriTemplate">14.4.4.2 Function <code>odata.fillUriTemplate</code></a></h4>
-<p>The <code>odata.fillUriTemplate</code> client-side function takes two or more expressions as arguments and returns a value of type <code>Edm.String.</code></p>
+<p>The <code>odata.fillUriTemplate</code> client-side function takes two or more expressions as arguments and returns a value of type <code>Edm.String</code>.</p>
 <p>The first argument MUST be of type <code>Edm.String</code> and specifies a URI template according to <a href="#rfc6570">RFC6570</a>, the other arguments MUST be <a href="#LabeledElement">labeled element expressions</a>. Each <a href="#LabeledElement">labeled element expression</a> specifies the template parameter name as its name and evaluates to the template parameter value.</p>
 <p><a href="#rfc6570">RFC6570</a> defines three kinds of template parameters: simple values, lists of values, and key-value maps.</p>
 <p>Simple values are represented as <a href="#LabeledElement">labeled element expressions</a> that evaluate to a single primitive value. The literal representation of this value according to <a href="#ODataABNF">OData-ABNF</a> is used to fill the corresponding template parameter.</p>

docs/odata-csdl-json/odata-csdl-json.md

@@ -4972,7 +4972,7 @@ the member name of the enumeration value.
 #### <a name="FunctionodatafillUriTemplate" href="#FunctionodatafillUriTemplate">14.4.4.2 Function `odata.fillUriTemplate`</a>
 
 The `odata.fillUriTemplate` client-side function takes two or more
-expressions as arguments and returns a value of type `Edm.String.`
+expressions as arguments and returns a value of type `Edm.String`.
 
 The first argument MUST be of type `Edm.String` and specifies a URI
 template according to [RFC6570](#rfc6570), the other arguments MUST be

docs/odata-csdl-xml/odata-csdl-xml.html

@@ -774,7 +774,7 @@ <h3 id="-element-edmxedmx"><a name="ElementedmxEdmx2" href="#ElementedmxEdmx2">
 <p>The <code>edmx:Edmx</code> element is the root element of a CSDL XML document. It MUST contain the <code>Version</code> attribute and it MUST contain exactly one <code>edmx:DataServices</code> element.</p>
 <p>It MAY contain <a href="#Reference"><code>edmx:Reference</code></a> elements to reference other CSDL documents.</p>
 <h3 id="-attribute-version"><a name="AttributeVersion2.1" href="#AttributeVersion2.1"> Attribute <code>Version</code></a></h3>
-<p>The <code>Version</code> attribute specifies the OData protocol version of the service. For OData 4.0 responses the value of this attribute MUST be <code>4.0.</code> For OData 4.01 responses the value of this attribute MUST be <code>4.01.</code> Services MUST return an OData 4.0 response if the request was made with an <code>OData-MaxVersion </code>header with a value of <code>4.0</code>.</p>
+<p>The <code>Version</code> attribute specifies the OData protocol version of the service. For OData 4.0 responses the value of this attribute MUST be <code>4.0</code>. For OData 4.01 responses the value of this attribute MUST be <code>4.01</code>. Services MUST return an OData 4.0 response if the request was made with an <code>OData-MaxVersion </code>header with a value of <code>4.0</code>.</p>
 <h3 id="-element-edmxdataservices"><a name="ElementedmxDataServices3" href="#ElementedmxDataServices3"> Element <code>edmx:DataServices</code></a></h3>
 <p>The <code>edmx:DataServices</code> element MUST contain one or more <a href="#Schema"><code>edm:Schema</code></a> elements which define the schemas exposed by the OData service.</p>
 </div>
@@ -2801,7 +2801,7 @@ <h4 id="14441-canonical-functions"><a name="CanonicalFunctions" href="#Canonical
 </div>
 <p><code>ProductName</code> is of type <code>String</code>, <code>Quantity</code> in complex type <code>Available</code> is of type <code>Decimal</code>, and <code>Unit</code> in <code>Available</code> is of type enumeration, so the result of the <code>Path</code> expression is represented as the member name of the enumeration value.</p>
 <h4 id="14442-function-odatafilluritemplate"><a name="FunctionodatafillUriTemplate" href="#FunctionodatafillUriTemplate">14.4.4.2 Function <code>odata.fillUriTemplate</code></a></h4>
-<p>The <code>odata.fillUriTemplate</code> client-side function takes two or more expressions as arguments and returns a value of type <code>Edm.String.</code></p>
+<p>The <code>odata.fillUriTemplate</code> client-side function takes two or more expressions as arguments and returns a value of type <code>Edm.String</code>.</p>
 <p>The first argument MUST be of type <code>Edm.String</code> and specifies a URI template according to <a href="#rfc6570">RFC6570</a>, the other arguments MUST be <a href="#LabeledElement">labeled element expressions</a>. Each <a href="#LabeledElement">labeled element expression</a> specifies the template parameter name as its name and evaluates to the template parameter value.</p>
 <p><a href="#rfc6570">RFC6570</a> defines three kinds of template parameters: simple values, lists of values, and key-value maps.</p>
 <p>Simple values are represented as <a href="#LabeledElement">labeled element expressions</a> that evaluate to a single primitive value. The literal representation of this value according to <a href="#ODataABNF">OData-ABNF</a> is used to fill the corresponding template parameter.</p>

docs/odata-csdl-xml/odata-csdl-xml.md

@@ -852,8 +852,8 @@ other CSDL documents.
 
 The `Version` attribute specifies the OData protocol version of the
 service. For OData 4.0 responses the value of this attribute MUST be
-`4.0.` For OData 4.01 responses the value of this attribute MUST be
-`4.01.` Services MUST return an OData 4.0 response if the request was
+`4.0`. For OData 4.01 responses the value of this attribute MUST be
+`4.01`. Services MUST return an OData 4.0 response if the request was
 made with an `OData-MaxVersion `header with a value of `4.0`.
 
 ### <a name="ElementedmxDataServices3" href="#ElementedmxDataServices3"> Element `edmx:DataServices`</a>
@@ -4802,7 +4802,7 @@ the member name of the enumeration value.
 #### <a name="FunctionodatafillUriTemplate" href="#FunctionodatafillUriTemplate">14.4.4.2 Function `odata.fillUriTemplate`</a>
 
 The `odata.fillUriTemplate` client-side function takes two or more
-expressions as arguments and returns a value of type `Edm.String.`
+expressions as arguments and returns a value of type `Edm.String`.
 
 The first argument MUST be of type `Edm.String` and specifies a URI
 template according to [RFC6570](#rfc6570), the other arguments MUST be

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

@@ -416,7 +416,7 @@ <h1 id="4-common-characteristics"><a name="CommonCharacteristics" href="#CommonC
 <p>This section describes common characteristics of the representation for OData values in JSON. A request or response body consists of several parts. It contains OData values as part of a larger document. Requests and responses are structured almost identical; the few existing differences will be explicitly called out in the respective subsections.</p>
 <h2 id="41-header-content-type"><a name="HeaderContentType" href="#HeaderContentType">4.1 Header Content-Type</a></h2>
 <p>Requests and responses with a JSON message body MUST have a <code>Content-Type</code> header value of <code>application/json</code>.</p>
-<p>Requests MAY add the <code>charset</code> parameter to the content type. Allowed values are <code>UTF-8</code>,<code> UTF-16</code>, and <code>UTF-32</code>. If no <code>charset</code> parameter is present, <code>UTF-8</code> MUST be assumed.</p>
+<p>Requests MAY add the <code>charset</code> parameter to the content type. Allowed values are <code>UTF-8</code>, <code>UTF-16</code>, and <code>UTF-32</code>. If no <code>charset</code> parameter is present, <code>UTF-8</code> MUST be assumed.</p>
 <p>Responses MUST include the <a href="#ControllingtheAmountofControlInformationinResponses"><code>metadata</code></a> parameter to specify the amount of metadata included in the response.</p>
 <p>Requests and responses MUST include the <a href="#ControllingtheRepresentationofNumbers"><code>IEEE754Compatible</code></a> parameter if <code>Edm.Int64</code> and <code>Edm.Decimal</code> numbers are represented as strings.</p>
 <p>Requests and responses MAY add the <code>streaming</code> parameter with a value of <code>true</code> or <code>false</code>, see section "<a href="#PayloadOrderingConstraints">Payload Ordering Constraints</a>".</p>
@@ -1256,7 +1256,7 @@ <h2 id="153-deleted-entity"><a name="DeletedEntity" href="#DeletedEntity">15.3 D
 <p>In OData 4.01 payloads the deleted-entity object MUST include the following properties, regardless of the specified <a href="#ControllingtheAmountofControlInformationinResponses"><code>metadata</code></a> value:</p>
 <ul>
 <li><p>Control information <a href="#ControlInformationremovedodataremoved"><code>removed</code></a>, whose value is an object that MAY contain a property named <code>reason</code>. If present, the value of <code>reason</code> MUST be either <code>deleted</code> if the entity was deleted (destroyed), or <code>changed</code> if the entity was removed from membership in the result either due to change in value such that the entity no longer matches the defining query or because the entity was removed from the collection. The object MAY include <a href="#InstanceAnnotations">annotations</a>, and clients SHOULD NOT error due to the presence of additional properties that MAY be defined by future versions of this specification. For <a href="#PayloadOrderingConstraints">ordered payloads</a>, the control information <a href="#ControlInformationremovedodataremoved"><code>removed</code></a> MUST immediately follow the <a href="#ControlInformationcontextodatacontext"><code>context</code></a> control information, if present, otherwise it MUST be the first property in the deleted entity.</p></li>
-<li><p>Control information <a href="#ControlInformationidodataid"><code>id</code></a> or all of the entity's key fields. The <code>id</code> control information MUST appear if any of the entity's key fields are omitted from the response <em>or</em> the entity-id is not identical to the canonical URL of the entity. For <a href="#PayloadOrderingConstraints">ordered payloads</a>, the control information <code>id,</code> if present, MUST immediately follow the control information <a href="#ControlInformationremovedodataremoved"><code>removed</code></a>.</p></li>
+<li><p>Control information <a href="#ControlInformationidodataid"><code>id</code></a> or all of the entity's key fields. The <code>id</code> control information MUST appear if any of the entity's key fields are omitted from the response <em>or</em> the entity-id is not identical to the canonical URL of the entity. For <a href="#PayloadOrderingConstraints">ordered payloads</a>, the control information <code>id</code>, if present, MUST immediately follow the control information <a href="#ControlInformationremovedodataremoved"><code>removed</code></a>.</p></li>
 </ul>
 <p>For full metadata the <a href="#ControlInformationcontextodatacontext"><code>context</code></a> control information MUST be included. It also MUST be included if the entity set of the deleted entity cannot be determined from the surrounding context.</p>
 <p>The deleted-entity object MAY include additional properties of the entity, as well as <a href="#InstanceAnnotations">annotations</a>, and MAY include related entities, related deleted entities, or a delta or full representation of a related collection of entities, to represent related entities that have been modified or deleted.</p>

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

@@ -551,7 +551,7 @@ Requests and responses with a JSON message body MUST have a
 `Content-Type` header value of `application/json`.
 
 Requests MAY add the `charset` parameter to the content type.
-Allowed values are `UTF-8`,` UTF-16`, and
+Allowed values are `UTF-8`, `UTF-16`, and
 `UTF-32`. If no `charset` parameter is present,
 `UTF-8` MUST be assumed.
 
@@ -2383,7 +2383,7 @@ following properties, regardless of the specified
   from the response _or_ the entity-id is not identical to the canonical
   URL of the entity. For [ordered
   payloads](#PayloadOrderingConstraints), the control information
-  `id,` if present, MUST immediately follow the control
+  `id`, if present, MUST immediately follow the control
   information
   [`removed`](#ControlInformationremovedodataremoved).