Avoid use of ′ in Markdown files

docs/odata-protocol/odata-protocol.html

@@ -2807,7 +2807,7 @@ <h3 id="1153-advertising-available-operations-within-a-payload"><a name="Adverti
 </summary>
 <p>Services MAY return actions and/or functions bound to a particular entity or entity collection as part of the representation of the entity or entity collection within the payload. The representation of an action or function depends on the <a href="#Formats">format</a>.</p>
 <div class="example">
-<p>Example 91: given a <code>GET</code> request to <code>http://host/service/Customers(′ALFKI′)</code>, the service might respond with a Customer that includes the <code>SampleEntities.MostRecentOrder</code> function bound to the entity</p>
+<p>Example 91: given a <code>GET</code> request to <code>http://host/service/Customers('ALFKI')</code>, the service might respond with a Customer that includes the <code>SampleEntities.MostRecentOrder</code> function bound to the entity</p>
 <div class="sourceCode" id="cb112"><pre class="sourceCode json"><code class="sourceCode json"><span id="cb112-1"><a href="#cb112-1" aria-hidden="true" tabindex="-1"></a><span class="fu">{</span></span>
 <span id="cb112-2"><a href="#cb112-2" aria-hidden="true" tabindex="-1"></a>  <span class="dt">&quot;@context&quot;</span><span class="fu">:</span> <span class="er">…</span><span class="fu">,</span></span>
 <span id="cb112-3"><a href="#cb112-3" aria-hidden="true" tabindex="-1"></a>  <span class="dt">&quot;CustomerID&quot;</span><span class="fu">:</span> <span class="st">&quot;ALFKI&quot;</span><span class="fu">,</span></span>
@@ -2919,7 +2919,7 @@ <h4 id="11551-invoking-an-action"><a name="InvokinganAction" href="#InvokinganAc
 <p>Actions without a return type respond with <a href="#ResponseCode204NoContent"><code>204 No Content</code></a> on success.</p>
 <p>To request processing of the action only if the binding parameter value, an entity or collection of entities, is unmodified, the client includes the <a href="#HeaderIfMatch"><code>If-Match</code></a> header with the latest known ETag value for the entity or collection of entities. The ETag value for a collection as a whole is transported in the <a href="#HeaderETag"><code>ETag</code></a> header of a collection response.</p>
 <div class="example">
-<p>Example 98: invoke the <code>SampleEntities.CreateOrder</code> action using <code>Customers(′ALFKI′)</code> as the customer (or binding parameter). The values <code>2</code> for the <code>quantity</code> parameter and <code>BLACKFRIDAY</code> for the <code>discountCode</code> parameter are passed in the body of the request. Invoke the action only if the customer’s ETag still matches.</p>
+<p>Example 98: invoke the <code>SampleEntities.CreateOrder</code> action using <code>Customers('ALFKI')</code> as the customer (or binding parameter). The values <code>2</code> for the <code>quantity</code> parameter and <code>BLACKFRIDAY</code> for the <code>discountCode</code> parameter are passed in the body of the request. Invoke the action only if the customer’s ETag still matches.</p>
 <div class="sourceCode" id="cb119"><pre class="sourceCode json"><code class="sourceCode json"><span id="cb119-1"><a href="#cb119-1" aria-hidden="true" tabindex="-1"></a><span class="er">POST</span> <span class="er">http://host/service/Customers(&#39;ALFKI&#39;)/SampleEntities.CreateOrder</span></span>
 <span id="cb119-2"><a href="#cb119-2" aria-hidden="true" tabindex="-1"></a><span class="er">If-Match:</span> <span class="er">W/&quot;MjAxOS0wMy0yMVQxMzowNVo=&quot;</span></span>
 <span id="cb119-3"><a href="#cb119-3" aria-hidden="true" tabindex="-1"></a><span class="er">Content-Type:</span> <span class="er">application/json</span></span>
@@ -3197,7 +3197,7 @@ <h4 id="11772-referencing-new-entities"><a name="ReferencingNewEntities" href="#
 …
 --changeset_77162fcd-b8da-41ac-a9f8-9357efbbe--
 --batch_36522ad7-fc75-4b56-8c71-56071383e77a--</code></pre>
-<p>The second <code>Location</code> URL <code>Orders(1)</code> is relative with its base URI being the second request URL <code>$1/Orders</code>. To get an absolute base URI, the client must replace the <code>$1</code> with the first <code>Location</code> URL <code>Customers(′ALFKI′)</code> and resolve the resulting URL <code>Customers(′ALFKI′)/Orders(1)</code> relative to its base URI, which is <code>http://host/service/Customers</code> (determined from the first request URL <code>/service/Customers</code> and the <code>Host: host</code> header as in <a href="#batchhost">example 102</a>). This gives the effective second request URL <code>http://host/service/Customers(′ALFKI′)/Orders</code> as base URI for the second <code>Location</code> URL, which therefore resolves to <code>http://host/service/Customers(′ALFKI′)/Orders(1)</code>.</p>
+<p>The second <code>Location</code> URL <code>Orders(1)</code> is relative with its base URI being the second request URL <code>$1/Orders</code>. To get an absolute base URI, the client must replace the <code>$1</code> with the first <code>Location</code> URL <code>Customers('ALFKI')</code> and resolve the resulting URL <code>Customers('ALFKI')/Orders(1)</code> relative to its base URI, which is <code>http://host/service/Customers</code> (determined from the first request URL <code>/service/Customers</code> and the <code>Host: host</code> header as in <a href="#batchhost">example 102</a>). This gives the effective second request URL <code>http://host/service/Customers('ALFKI')/Orders</code> as base URI for the second <code>Location</code> URL, which therefore resolves to <code>http://host/service/Customers('ALFKI')/Orders(1)</code>.</p>
 </div>
 </details>
 <details open><summary>

docs/odata-protocol/odata-protocol.md

@@ -5372,7 +5372,7 @@ or function depends on the [format](#Formats).
 
 ::: example
 Example 91: given a `GET` request to
-`http://host/service/Customers(′ALFKI′)`, the service might respond with
+`http://host/service/Customers('ALFKI')`, the service might respond with
 a Customer that includes the `SampleEntities.MostRecentOrder` function
 bound to the entity
 ```json
@@ -5714,7 +5714,7 @@ collection response.
 
 ::: example
 Example 98: invoke the `SampleEntities.CreateOrder` action using
-`Customers(′ALFKI′)` as the customer (or binding parameter). The values
+`Customers('ALFKI')` as the customer (or binding parameter). The values
 `2` for the `quantity` parameter and `BLACKFRIDAY` for the
 `discountCode` parameter are passed in the body of the request. Invoke
 the action only if the customer's ETag still matches.
@@ -6225,13 +6225,13 @@ Location: Orders(1)
 ```
 The second `Location` URL `Orders(1)` is relative with its base URI being the second
 request URL `$1/Orders`. To get an absolute base URI, the client must replace the
-`$1` with the first `Location` URL `Customers(′ALFKI′)` and resolve the
-resulting URL `Customers(′ALFKI′)/Orders(1)` relative to its base URI, which is
+`$1` with the first `Location` URL `Customers('ALFKI')` and resolve the
+resulting URL `Customers('ALFKI')/Orders(1)` relative to its base URI, which is
 `http://host/service/Customers` (determined from the
 first request URL `/service/Customers` and the `Host: host` header
 as in [example 102](#batchhost)). This gives the effective second request URL
-`http://host/service/Customers(′ALFKI′)/Orders` as base URI for the second `Location`
-URL, which therefore resolves to `http://host/service/Customers(′ALFKI′)/Orders(1)`.
+`http://host/service/Customers('ALFKI')/Orders` as base URI for the second `Location`
+URL, which therefore resolves to `http://host/service/Customers('ALFKI')/Orders(1)`.
 :::
 
 #### <a name="ReferencinganETag" href="#ReferencinganETag">11.7.7.3 Referencing an ETag</a>

docs/odata-url-conventions/odata-url-conventions.html

@@ -2420,7 +2420,7 @@ <h4 id="5181-search-expressions"><a name="SearchExpressions" href="#SearchExpres
 <p>Expressions prefaced with <code>NOT</code> evaluate to <code>true</code> if the expression is not matched, otherwise <code>false</code>.</p>
 <p>Two expressions not enclosed in quotes and separated by a space are equivalent to the same two expressions separated by the <code>AND</code> keyword. Such expressions evaluate to <code>true</code> if both expressions evaluate to <code>true</code>, otherwise <code>false</code>.</p>
 <p>Expressions separated by an <code>OR</code> evaluate to <code>true</code> if either of the expressions evaluate to <code>true</code>, otherwise <code>false</code>.</p>
-<p>To support type-ahead use cases, incomplete search expressions can be sent as OData string literals enclosed in single-quotes, and single-quotes within the search expression doubled. Such an expression can also be used to search for double quotes: <code>?$search=′"′</code>.</p>
+<p>To support type-ahead use cases, incomplete search expressions can be sent as OData string literals enclosed in single-quotes, and single-quotes within the search expression doubled. Such an expression can also be used to search for double quotes: <code>?$search='"'</code>.</p>
 <p>The <a href="#ODataABNF">OData-ABNF</a> <code>searchExpr</code> syntax rule defines the formal grammar of the search expression.</p>
 </details>
 </details>

docs/odata-url-conventions/odata-url-conventions.md

@@ -4042,7 +4042,7 @@ expressions evaluate to `true`, otherwise `false`.
 To support type-ahead use cases, incomplete search expressions can be
 sent as OData string literals enclosed in single-quotes, and
 single-quotes within the search expression doubled.
-Such an expression can also be used to search for double quotes: `?$search=′"′`.
+Such an expression can also be used to search for double quotes: `?$search='"'`.
 
 The [OData-ABNF](#ODataABNF) `searchExpr` syntax rule defines the formal
 grammar of the search expression.

odata-protocol/11.5 Operations.md

@@ -103,7 +103,7 @@ or function depends on the [format](#Formats).
 
 ::: example
 Example ##ex: given a `GET` request to
-`http://host/service/Customers(′ALFKI′)`, the service might respond with
+`http://host/service/Customers('ALFKI')`, the service might respond with
 a Customer that includes the `SampleEntities.MostRecentOrder` function
 bound to the entity
 ```json
@@ -445,7 +445,7 @@ collection response.
 
 ::: example
 Example ##ex: invoke the `SampleEntities.CreateOrder` action using
-`Customers(′ALFKI′)` as the customer (or binding parameter). The values
+`Customers('ALFKI')` as the customer (or binding parameter). The values
 `2` for the `quantity` parameter and `BLACKFRIDAY` for the
 `discountCode` parameter are passed in the body of the request. Invoke
 the action only if the customer's ETag still matches.

odata-protocol/11.7 Batch Requests.md

@@ -404,13 +404,13 @@ Location: Orders(1)
 ```
 The second `Location` URL `Orders(1)` is relative with its base URI being the second
 request URL `$1/Orders`. To get an absolute base URI, the client must replace the
-`$1` with the first `Location` URL `Customers(′ALFKI′)` and resolve the
-resulting URL `Customers(′ALFKI′)/Orders(1)` relative to its base URI, which is
+`$1` with the first `Location` URL `Customers('ALFKI')` and resolve the
+resulting URL `Customers('ALFKI')/Orders(1)` relative to its base URI, which is
 `http://host/service/Customers` (determined from the
 first request URL `/service/Customers` and the `Host: host` header
 as in [example ##batchhost]). This gives the effective second request URL
-`http://host/service/Customers(′ALFKI′)/Orders` as base URI for the second `Location`
-URL, which therefore resolves to `http://host/service/Customers(′ALFKI′)/Orders(1)`.
+`http://host/service/Customers('ALFKI')/Orders` as base URI for the second `Location`
+URL, which therefore resolves to `http://host/service/Customers('ALFKI')/Orders(1)`.
 :::
 
 #### ##subsubsubsec Referencing an ETag

odata-url-conventions/5 Query Options.md

@@ -2469,7 +2469,7 @@ expressions evaluate to `true`, otherwise `false`.
 To support type-ahead use cases, incomplete search expressions can be
 sent as OData string literals enclosed in single-quotes, and
 single-quotes within the search expression doubled.
-Such an expression can also be used to search for double quotes: `?$search=′"′`.
+Such an expression can also be used to search for double quotes: `?$search='"'`.
 
 The [OData-ABNF](#ODataABNF) `searchExpr` syntax rule defines the formal
 grammar of the search expression.