curly -> straight apostrophes (mdn#16770)

* Replace curly apostrophes by regular apostrophes.
 Adding to mdn#16324.

* fix a typo

Author: OnkarRuikar

files/en-us/web/html/element/input/number/index.md

@@ -419,7 +419,7 @@ After declaring a few variables, an event listener is added to the `button` to c
 
 ## Accessibility
 
-The implicit [role](/en-US/docs/Web/Accessibility/ARIA/Roles) for the `<input type="number">` element is [`spinbutton`](/en-US/docs/Web/Accessibility/ARIA/Roles/spinbutton_role). If spinbutton is not an important feature for your form control, consider *not* using `type="number"`. Instead, use [`inputmode="numeric"`](/en-US/docs/Web/HTML/Global_attributes/inputmode) along with a [`pattern`](/en-US/docs/Web/HTML/Attributes/pattern) attribute that limits the characters to numbers and associated characters. With `<input type="number">`, there is a risk of users accidentally incrementing a number when they’re trying to do something else. Additionally, if users try to enter something that’s not a number, there’s no explicit feedback about what they’re doing wrong.
+The implicit [role](/en-US/docs/Web/Accessibility/ARIA/Roles) for the `<input type="number">` element is [`spinbutton`](/en-US/docs/Web/Accessibility/ARIA/Roles/spinbutton_role). If spinbutton is not an important feature for your form control, consider *not* using `type="number"`. Instead, use [`inputmode="numeric"`](/en-US/docs/Web/HTML/Global_attributes/inputmode) along with a [`pattern`](/en-US/docs/Web/HTML/Attributes/pattern) attribute that limits the characters to numbers and associated characters. With `<input type="number">`, there is a risk of users accidentally incrementing a number when they're trying to do something else. Additionally, if users try to enter something that's not a number, there's no explicit feedback about what they're doing wrong.
 
 Also consider using the [`autocomplete`](/en-US/docs/Web/HTML/Attributes/autocomplete) attribute to help users complete forms more quickly and with fewer chances of errors. For example, to enable autofill on a zip code field, set `autocomplete="postal-code"`.
 

files/en-us/web/html/element/source/index.md

@@ -80,12 +80,12 @@ This element includes the [global attributes](/en-US/docs/Web/HTML/Global_attrib
   - : The [MIME media type of the resource](/en-US/docs/Web/Media/Formats/Image_types), optionally with a [`codecs` parameter](/en-US/docs/Web/Media/Formats/codecs_parameter).
 
 - {{htmlattrdef("src")}}
-  - : Required if the `source` element’s parent is an {{HTMLElement("audio")}} and {{HTMLElement("video")}} element, but not allowed if the `source` element’s parent is a {{HTMLElement("picture")}} element.
+  - : Required if the `source` element's parent is an {{HTMLElement("audio")}} and {{HTMLElement("video")}} element, but not allowed if the `source` element's parent is a {{HTMLElement("picture")}} element.
 
     Address of the media resource.
 
 - {{htmlattrdef("srcset")}}
-  - : Required if the `source` element’s parent is a {{HTMLElement("picture")}} element, but not allowed if the `source` element’s parent is an {{HTMLElement("audio")}} or {{HTMLElement("video")}} element.
+  - : Required if the `source` element's parent is a {{HTMLElement("picture")}} element, but not allowed if the `source` element's parent is an {{HTMLElement("audio")}} or {{HTMLElement("video")}} element.
 
     A list of one or more strings, separated by commas, indicating a set of possible images represented by the source for the browser to use. Each string is composed of:
 
@@ -96,22 +96,22 @@ This element includes the [global attributes](/en-US/docs/Web/HTML/Global_attrib
     Each string in the list must have at least a width descriptor or a pixel density descriptor to be valid. Among the list, there must be only one string containing the same tuple of width descriptor and pixel density descriptor. The browser chooses the most adequate image to display at a given point of time.
 
 - {{htmlattrdef("sizes")}}
-  - : Allowed if the `source` element’s parent is a {{HTMLElement("picture")}} element, but not allowed if the `source` element’s parent is an {{HTMLElement("audio")}} or {{HTMLElement("video")}} element.
+  - : Allowed if the `source` element's parent is a {{HTMLElement("picture")}} element, but not allowed if the `source` element's parent is an {{HTMLElement("audio")}} or {{HTMLElement("video")}} element.
 
     A list of source sizes that describes the final rendered width of the image represented by the source. Each source size consists of a comma-separated list of media condition-length pairs. This information is used by the browser to determine, before laying the page out, which image defined in {{htmlattrxref("srcset", "source")}} to use. Please note that `sizes` will have its effect only if width dimension descriptors are provided with `srcset` instead of pixel ratio values (200w instead of 2x for example).
 
 - {{htmlattrdef("media")}}
-  - : Allowed if the `source` element’s parent is a {{HTMLElement("picture")}} element, but not allowed if the `source` element’s parent is an {{HTMLElement("audio")}} or {{HTMLElement("video")}} element.
+  - : Allowed if the `source` element's parent is a {{HTMLElement("picture")}} element, but not allowed if the `source` element's parent is an {{HTMLElement("audio")}} or {{HTMLElement("video")}} element.
 
     [Media query](/en-US/docs/Web/CSS/Media_Queries) of the resource's intended media.
 
 - {{htmlattrdef("height")}}
-  - : Allowed if the `source` element’s parent is a {{HTMLElement("picture")}} element, but not allowed if the `source` element’s parent is an {{HTMLElement("audio")}} or {{HTMLElement("video")}} element.
+  - : Allowed if the `source` element's parent is a {{HTMLElement("picture")}} element, but not allowed if the `source` element's parent is an {{HTMLElement("audio")}} or {{HTMLElement("video")}} element.
 
     The intrinsic height of the image, in pixels. Must be an integer without a unit.
 
 - {{htmlattrdef("width")}}
-  - : Allowed if the `source` element’s parent is a {{HTMLElement("picture")}} element, but not allowed if the `source` element’s parent is an {{HTMLElement("audio")}} or {{HTMLElement("video")}} element.
+  - : Allowed if the `source` element's parent is a {{HTMLElement("picture")}} element, but not allowed if the `source` element's parent is an {{HTMLElement("audio")}} or {{HTMLElement("video")}} element.
 
     The intrinsic width of the image in pixels. Must be an integer without a unit.
 

files/en-us/web/http/basics_of_http/mime_types/index.md

@@ -156,7 +156,7 @@ Per the current relevant standards, JavaScript content should always be served u
 No other MIME types are considered valid for JavaScript, and using any MIME type other than`text/javascript` may result in scripts that do not load or run.
 
 You may find some JavaScript content incorrectly served with a `charset` parameter as part of the MIME type — as an attempt to specify the character set for the script content.
-That `charset` parameter isn’t valid for JavaScript content, and in most cases will result in a script failing to load.
+That `charset` parameter isn't valid for JavaScript content, and in most cases will result in a script failing to load.
 
 #### Legacy JavaScript MIME types
 

files/en-us/web/http/caching/index.md

@@ -39,7 +39,7 @@ Personalized contents are usually controlled by cookies, but the presence of a c
 
 Also, since the private cache requires `private`, you may think that the shared cache requires `public` — but that is not quite true. A shared cache will store a response without needing `public` as long as `max-age` is given.
 
-If the response has an `Authorization` header, it cannot be stored in either the private cache or the shared cache, even if it has `max-age` — and `public` can be used to allow such a case. But if you are not using basic authentication and do not have an `Authorization` header, then there is no need to add `public`; it’s just a waste of bytes in that case.
+If the response has an `Authorization` header, it cannot be stored in either the private cache or the shared cache, even if it has `max-age` — and `public` can be used to allow such a case. But if you are not using basic authentication and do not have an `Authorization` header, then there is no need to add `public`; it's just a waste of bytes in that case.
 
 ### Shared cache
 
@@ -75,7 +75,7 @@ Cache-Control: no-store
 
 For example, Varnish uses VCL-based logic to handle cache storage, while service workers in combination with the Cache API allow you to create that logic in JavaScript.
 
-That means if a managed cache intentionally ignores a `no-store` directive, there is no need to perceive it as being "non-compliant" with the standard. What you should do is, avoid using kitchen-sink headers, but carefully read the documentation of whatever managed-cache mechanism you’re using, and ensure you’re controlling the cache properly in the ways provided by the mechanism you’ve chosen to use.
+That means if a managed cache intentionally ignores a `no-store` directive, there is no need to perceive it as being "non-compliant" with the standard. What you should do is, avoid using kitchen-sink headers, but carefully read the documentation of whatever managed-cache mechanism you're using, and ensure you're controlling the cache properly in the ways provided by the mechanism you've chosen to use.
 
 Note that some CDNs provide their own headers that are effective only for that CDN (for example, `Surrogate-Control`). Currently, work is underway to define a [`CDN-Cache-Control`](https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-targeted-cache-control) header to standardize those.
 
@@ -208,7 +208,7 @@ If-Modified-Since: Tue, 22 Feb 2022 22:00:00 GMT
 
 The server will respond with `304 Not Modified` if the content has not changed since the specified time.
 
-Since this response only indicates "no change", there is no response body — instead there’s just a status code — so the transfer size is extremely small.
+Since this response only indicates "no change", there is no response body — instead there's just a status code — so the transfer size is extremely small.
 
 ```http
 HTTP/1.1 304 Not Modified
@@ -290,13 +290,13 @@ Cache-Control: max-age=0, must-revalidate
 
 However, that usage of `max-age=0` is a remnant of the fact that many implementations prior to HTTP/1.1 were unable to handle the `no-cache` directive — and so to deal with that limitation, `max-age=0` was used as a workaround.
 
-But now that HTTP/1.1-conformant servers are widely deployed, there’s no reason to ever use that `max-age=0`-and-`must-revalidate` combination — you should instead just use `no-cache`.
+But now that HTTP/1.1-conformant servers are widely deployed, there's no reason to ever use that `max-age=0`-and-`must-revalidate` combination — you should instead just use `no-cache`.
 
 ## Don't cache
 
 The `no-cache` directive does not prevent storage of responses, but instead prevents reuse of responses without revalidation.
 
-If you don’t want a response stored in any cache, use `no-store`.
+If you don't want a response stored in any cache, use `no-store`.
 
 ```http
 Cache-Control: no-store
@@ -358,7 +358,7 @@ Cache-Control: no-cache, private
 
 You may think adding `no-store` would be the right way to opt out from caching.
 
-However, it’s basically not recommended to grant `no-store` easily, because you lose many advantages that HTTP and browsers have, including the browser’s back/forward cache.
+However, it's basically not recommended to grant `no-store` easily, because you lose many advantages that HTTP and browsers have, including the browser's back/forward cache.
 
 Therefore, to get the advantages of the full feature set of the web platform, prefer the use of `no-cache` in combination with `private`.
 
@@ -410,7 +410,7 @@ Cache-Control: no-cache
 
 (The requests from Chrome, Edge, and Firefox look very much like the above; the requests from Safari will look a bit different.)
 
-Since that’s not a conditional request with `no-cache`, you can be sure you’ll get a `200 OK` from the origin server.
+Since that's not a conditional request with `no-cache`, you can be sure you'll get a `200 OK` from the origin server.
 
 That behavior is also defined in the [Fetch](https://fetch.spec.whatwg.org/#http-network-or-cache-fetch) standard and can be reproduced in JavaScript by calling `fetch()` with the cache mode set to `reload` (note that it's not `force-reload`):
 
@@ -455,7 +455,7 @@ You may want to overwrite that response once it expired on the server, but there
 
 One of the methods mentioned in the specification is to send a request for the same URL with an unsafe method such as `POST` — but that is usually difficult to do so intentionally in many clients.
 
-There is also a specification for a `Clear-Site-Data: cache` header and value, but [not all browsers support it](https://groups.google.com/a/mozilla.org/g/dev-platform/c/I939w1yrTp4) — and even when it’s used, it is only affects browser caches, but has no effect on intermediate caches.
+There is also a specification for a `Clear-Site-Data: cache` header and value, but [not all browsers support it](https://groups.google.com/a/mozilla.org/g/dev-platform/c/I939w1yrTp4) — and even when it's used, it is only affects browser caches, but has no effect on intermediate caches.
 
 Therefore, it should be assumed that any stored response will remain for its `max-age` period unless the user manually performs a reload, force reload, or clear-history action.
 
@@ -483,9 +483,9 @@ This section describes the common patterns in designing caches.
 
 As mentioned above, the default behavior for caching (that is, for a response without `Cache-Control`) is not simply "don't cache" but implicit caching according to so-called "heuristic caching".
 
-To avoid that heuristic caching, it’s preferable to explicitly give all responses a default `Cache-Control` header.
+To avoid that heuristic caching, it's preferable to explicitly give all responses a default `Cache-Control` header.
 
-To ensure that by default the latest versions of resources will always be transferred, it’s common practice to make the default `Cache-Control` value include `no-cache`:
+To ensure that by default the latest versions of resources will always be transferred, it's common practice to make the default `Cache-Control` value include `no-cache`:
 
 ```http
 Cache-Control: no-cache
@@ -578,7 +578,7 @@ Cache-Control: max-age=2592000
 
 ### Validation
 
-Don't forget to set the `If-Modified-Since` and `ETag` headers, so that you don't have to re-transmit a resource when reloading. It’s easy to generate those headers for pre-built static files.
+Don't forget to set the `If-Modified-Since` and `ETag` headers, so that you don't have to re-transmit a resource when reloading. It's easy to generate those headers for pre-built static files.
 
 The `ETag` value here may be a hash of the file.
 
@@ -605,7 +605,7 @@ ETag: YsAIAAAA-QG4G6kCMAMBAAAAAAAoK
 Making a response cacheable over a long period of time by changing the URL when the content changes is called **cache busting**. That technique can be applied to all subresources, such as images.
 
 > **Note:** When evaluating the use of `immutable` and QPACK:
-> If you’re concerned that `immutable` changes the predefined value provided by QPACK, consider that
+> If you're concerned that `immutable` changes the predefined value provided by QPACK, consider that
 > in this case, the `immutable` part can be encoded separately by splitting the `Cache-Control` value into two lines — though this is dependent on the encoding algorithm a particular QPACK implementation uses.
 
 ```http
@@ -640,7 +640,7 @@ If-Modified-Since: Tue, 22 Feb 2022 20:20:20 GMT
 ETag: AAPuIbAOdvAGEETbgAAAAAAABAAE
 ```
 
-That setting is appropriate for non-personalized HTML — but for a response which gets personalized using cookies (for example, after a login), don’t forget to also specify `private`:
+That setting is appropriate for non-personalized HTML — but for a response which gets personalized using cookies (for example, after a login), don't forget to also specify `private`:
 
 ```http
 200 OK HTTP/1.1
@@ -658,9 +658,9 @@ Most web content can be covered by a combination of the two patterns described a
 
 ### More about managed caches
 
-With the method described in previous sections, subresources can be cached for a long time by using cache busting, but main resources (which are usually HTML documents) can’t be.
+With the method described in previous sections, subresources can be cached for a long time by using cache busting, but main resources (which are usually HTML documents) can't be.
 
-Caching main resources is difficult because, using just standard directives from the HTTP Caching specification, there’s no way to actively delete cache contents when content is updated on the server.
+Caching main resources is difficult because, using just standard directives from the HTTP Caching specification, there's no way to actively delete cache contents when content is updated on the server.
 
 However, it is possible by deploying a managed cache such as a CDN or service worker.
 

files/en-us/web/http/headers/x-forwarded-for/index.md

@@ -18,7 +18,7 @@ The **`X-Forwarded-For`** (XFF) request header is a de-facto standard header for
 When a client connects directly to a server, the
 client's IP address is sent to the server (and is often written to server
 access logs). But if a client connection passes through any [forward or reverse](https://en.wikipedia.org/wiki/Proxy_server) proxies, the server only
-sees the final proxy's IP address, which is often of little use. That’s especially true if
+sees the final proxy's IP address, which is often of little use. That's especially true if
 the final proxy is a load balancer which is part of the same installation
 as the server. So, to provide a more-useful client IP address to the server, the `X-Forwarded-For` request header is
 used.
@@ -48,13 +48,13 @@ header.
 
 The `X-Forwarded-For` header is untrustworthy when no trusted reverse proxy (e.g., a load balancer) is between the client and
 server. If the client and all proxies are benign and well-behaved, then the list of IP addresses in the header
-has the meaning described in the [Directives](#directives) section. But if there’s a risk the client or any proxy
-is malicious or misconfigured, then it’s possible any part (or the entirety) of the header may have been
+has the meaning described in the [Directives](#directives) section. But if there's a risk the client or any proxy
+is malicious or misconfigured, then it's possible any part (or the entirety) of the header may have been
 spoofed (and may not be a list or contain IP addresses at all).
 
 If any trusted reverse proxies are between the client and
 server, the final `X-Forwarded-For` IP addresses (one for each trusted proxy) are trustworthy, as they
-were added by trusted proxies. (That’s true as long as the server is _only_
+were added by trusted proxies. (That's true as long as the server is _only_
 accessible through those proxies and not also directly).
 
 Any security-related use of `X-Forwarded-For` (such as for rate limiting or IP-based