From df6845965950fa24d0797309c38ffdf838a3fc0d Mon Sep 17 00:00:00 2001 From: OnkarRuikar <87750369+OnkarRuikar@users.noreply.github.com> Date: Mon, 11 Jul 2022 10:29:04 +0530 Subject: [PATCH 1/3] Correct usage of ellipsis, part 5 --- .../contribute/howto/write_an_api_reference/index.md | 2 +- files/en-us/mdn/contribute/markdown_in_mdn/index.md | 2 +- .../matching_features_to_browser_version/index.md | 2 +- files/en-us/mdn/guidelines/video/index.md | 2 +- .../en-us/mdn/guidelines/writing_style_guide/index.md | 8 ++++---- files/en-us/mdn/kitchensink/index.md | 1 - .../en-us/mdn/structures/compatibility_tables/index.md | 2 +- .../page_types/api_landing_page_template/index.md | 4 ++-- files/en-us/mdn/tools/unsupported_get_api/index.md | 4 ++-- .../webextensions/api/browsingdata/remove/index.md | 2 +- .../webextensions/api/browsingdata/settings/index.md | 2 +- .../mozilla/add-ons/webextensions/api/pkcs11/index.md | 4 ++-- .../api/userscripts/working_with_userscripts/index.md | 2 +- .../manifest.json/content_scripts/index.md | 4 ++-- files/en-us/mozilla/firefox/releases/6/index.md | 2 +- files/en-us/mozilla/firefox/releases/60/index.md | 2 +- files/en-us/mozilla/firefox/releases/61/index.md | 2 +- files/en-us/mozilla/firefox/releases/68/index.md | 2 +- files/en-us/related/criteria_for_inclusion/index.md | 2 +- files/en-us/related/project_guidelines/index.md | 4 ++-- files/en-us/web/api/abstractrange/index.md | 4 ++-- files/en-us/web/api/css_painting_api/guide/index.md | 2 +- .../web/api/document/requeststorageaccess/index.md | 2 +- files/en-us/web/api/document/xmlencoding/index.md | 4 ++-- files/en-us/web/api/fontfaceset/loading_event/index.md | 2 +- files/en-us/web/api/htmlmediaelement/autoplay/index.md | 2 -- .../index.md | 2 +- files/en-us/web/api/mutationevent/index.md | 1 - files/en-us/web/api/paymentresponse/retry/index.md | 2 +- .../permissions_api/using_the_permissions_api/index.md | 4 ++-- files/en-us/web/api/pushmessagedata/json/index.md | 2 +- files/en-us/web/api/rtcicecandidate/sdpmid/index.md | 6 +----- .../web/api/rtcicecandidate/sdpmlineindex/index.md | 4 ---- .../rtcremoteoutboundrtpstreamstats/localid/index.md | 7 +++---- .../web/api/webrtc_api/using_data_channels/index.md | 2 -- files/en-us/web/api/webvtt_api/index.md | 2 +- .../web/api/webxr_device_api/performance/index.md | 10 ++-------- files/en-us/web/api/xrrigidtransform/matrix/index.md | 2 +- files/en-us/web/css/@counter-style/index.md | 3 +-- files/en-us/web/css/@counter-style/pad/index.md | 2 +- files/en-us/web/css/@media/-ms-high-contrast/index.md | 3 +-- 41 files changed, 50 insertions(+), 73 deletions(-) diff --git a/files/en-us/mdn/contribute/howto/write_an_api_reference/index.md b/files/en-us/mdn/contribute/howto/write_an_api_reference/index.md index 6fabb7139db3c86..19d76bd754b5bb5 100644 --- a/files/en-us/mdn/contribute/howto/write_an_api_reference/index.md +++ b/files/en-us/mdn/contribute/howto/write_an_api_reference/index.md @@ -340,7 +340,7 @@ Method pages need the following sections: 5. **Syntax**: The syntax section should include a 2–3 line example — usually just construction of the interface, then calling of the interface method. - The syntax should be of the form: - - : method(param1, param2, ...) + - : method(param1, param2, …) The syntax section should include three subsections (see {{domxref("SubtleCrypto.sign()")}} for an example): diff --git a/files/en-us/mdn/contribute/markdown_in_mdn/index.md b/files/en-us/mdn/contribute/markdown_in_mdn/index.md index 3ed2183a6389295..2e4f9fb543a554f 100644 --- a/files/en-us/mdn/contribute/markdown_in_mdn/index.md +++ b/files/en-us/mdn/contribute/markdown_in_mdn/index.md @@ -205,7 +205,7 @@ For example, if we want to use "Warnung" for "Warning" in German, then in German > **Warnung:** So schreibt man eine Warnung. ``` -...and this will produce: +And this will produce: ```html
diff --git a/files/en-us/mdn/contribute/processes/matching_features_to_browser_version/index.md b/files/en-us/mdn/contribute/processes/matching_features_to_browser_version/index.md index ab8b7e827e88cfa..e6e6cec58432445 100644 --- a/files/en-us/mdn/contribute/processes/matching_features_to_browser_version/index.md +++ b/files/en-us/mdn/contribute/processes/matching_features_to_browser_version/index.md @@ -308,7 +308,7 @@ The [Searchfox](https://searchfox.org/) website provides another method you can ## Opera -_If you have insights into locating release versions for changes to Opera, please consider helping us write this section..._ +_If you have insights into locating release versions for changes to Opera, please consider helping us write this section…_ ### Presto diff --git a/files/en-us/mdn/guidelines/video/index.md b/files/en-us/mdn/guidelines/video/index.md index bc694083a59d81e..51bf51f8669c155 100644 --- a/files/en-us/mdn/guidelines/video/index.md +++ b/files/en-us/mdn/guidelines/video/index.md @@ -92,7 +92,7 @@ This actually provides pretty easy simple recording facilities too: 4. Press the _Start Recording_ button. 5. Perform whatever actions you want to record. 6. Press the _Stop_ button. -7. Choose _File_ > _Export As..._ > _1080p_ from the main menu to save as hi definition. +7. Choose _File_ > _Export As…_ > _1080p_ from the main menu to save as hi definition. ### Other resources diff --git a/files/en-us/mdn/guidelines/writing_style_guide/index.md b/files/en-us/mdn/guidelines/writing_style_guide/index.md index 0f18a0f94342cd5..5501b279c3068c9 100644 --- a/files/en-us/mdn/guidelines/writing_style_guide/index.md +++ b/files/en-us/mdn/guidelines/writing_style_guide/index.md @@ -117,7 +117,7 @@ Instead, the summary should focus on the `strokeText()` method, and should refer > If the value is `"left"`, the string is drawn starting at the specified value of `x`. > And if `textAlign` is `"right"`, the text is drawn such that it ends at the specified X-coordinate. > -> (etc etc etc...) +> (etc etc etc…) > > You can, optionally, provide a fourth parameter that lets you specify a maximum width for the string, in pixels. > If you provide this parameter, the text is compressed horizontally or scaled (or otherwise adjusted) to fit inside a space that wide when being drawn. @@ -288,7 +288,7 @@ They also ensure correct linking to detailed documentation. - : Use the [`htmlattrdef`](https://github.com/mdn/yari/blob/main/kumascript/macros/htmlattrdef.ejs) macro (e.g., `\{{htmlattrdef("type")}})` for the definition term, so that it can be linked to from other pages easily by using the [`htmlattrxref`](https://github.com/mdn/yari/blob/main/kumascript/macros/htmlattrxref.ejs) macro (e.g., `\{{htmlattrxref("type","element")}}`) to reference attribute definitions. - Attribute values - : Use the "Inline Code" style to apply `` to attribute values, and don't use quotation marks around string values, unless needed by the syntax of a code sample. - **For example:** "When the `type` attribute of an `` element is set to `email` or `tel` ..." + **For example:** "When the `type` attribute of an `` element is set to `email` or `tel`…" ### Latin abbreviations @@ -342,8 +342,8 @@ Use full capitals and delete periods in all acronyms and abbreviations, includin On the first mention of a term on a page, expand acronyms that are likely to be unfamiliar to users. When in doubt, expand it—or better yet, link it to the article or [glossary](/en-US/docs/Glossary) entry describing the technology. -- **Correct**: "XUL (XML User Interface Language) is Mozilla's XML-based language..." -- **Incorrect**: "XUL is Mozilla's XML-based language..." +- **Correct**: "XUL (XML User Interface Language) is Mozilla's XML-based language…" +- **Incorrect**: "XUL is Mozilla's XML-based language…" #### Plurals of acronyms and abbreviations diff --git a/files/en-us/mdn/kitchensink/index.md b/files/en-us/mdn/kitchensink/index.md index 835dcee3ad7e1d8..67966e908dc0dd4 100644 --- a/files/en-us/mdn/kitchensink/index.md +++ b/files/en-us/mdn/kitchensink/index.md @@ -234,7 +234,6 @@ When you request to access a {{Glossary("URL")}}, the gateway server can relay y - JavaScript {{jsxref("Array")}} on MDN Listening for mouse movement is even easier than listening for key presses: all we need is the listener for the {{domxref("Element/mousemove_event", "mousemove")}} event. -...just below the `keyup event`: ## Browser compatibility diff --git a/files/en-us/mdn/structures/compatibility_tables/index.md b/files/en-us/mdn/structures/compatibility_tables/index.md index 96d99e6cb600286..01c1e4f86382dc2 100644 --- a/files/en-us/mdn/structures/compatibility_tables/index.md +++ b/files/en-us/mdn/structures/compatibility_tables/index.md @@ -74,7 +74,7 @@ Now, whenever you want to update your fork, you can do so by: Next, go to your remote fork (it will be at `https://github.com/your-username/browser-compat-data`) and create a new branch to store your changes for this data addition. This can be done by: 1. Clicking on the "Branch: Main" button. -2. Entering a new branch name into the "Find or create a branch..." text field. +2. Entering a new branch name into the "Find or create a branch…" text field. 3. Pressing the resulting "Create branch _name-of-branch_ from Main" button. For example, if you were wanting to add data for the WebVR API, you'd create a branch called something like "webvr". diff --git a/files/en-us/mdn/structures/page_types/api_landing_page_template/index.md b/files/en-us/mdn/structures/page_types/api_landing_page_template/index.md index d5d75c30217faf2..440d66202a4dbc4 100644 --- a/files/en-us/mdn/structures/page_types/api_landing_page_template/index.md +++ b/files/en-us/mdn/structures/page_types/api_landing_page_template/index.md @@ -109,8 +109,8 @@ In this section, describe the API's purpose and usage cases in a bit more detail What problems does it solve? What concepts does it involve? How do you use it, from a high level perspective? Don't go into a lot of detail in this section, and don't include code examples. -If there are a lot of concepts to explain around this API, you should explain them in a separate "Fundamentals ..." or "Concepts..." article (e.g. [Fundamentals of WebXR](/en-US/docs/Web/API/WebXR_Device_API/Fundamentals)). -For a practical usage guide with code examples, you should include a "Usage..." article in your API docs (e.g. [Using the WebVR API](/en-US/docs/Web/API/WebVR_API/Using_the_WebVR_API)). +If there are a lot of concepts to explain around this API, you should explain them in a separate "Fundamentals …" or "Concepts…" article (e.g. [Fundamentals of WebXR](/en-US/docs/Web/API/WebXR_Device_API/Fundamentals)). +For a practical usage guide with code examples, you should include a "Usage…" article in your API docs (e.g. [Using the WebVR API](/en-US/docs/Web/API/WebVR_API/Using_the_WebVR_API)). To help improve content discoverability and {{Glossary("SEO")}}, keep the following tips in mind: diff --git a/files/en-us/mdn/tools/unsupported_get_api/index.md b/files/en-us/mdn/tools/unsupported_get_api/index.md index 498e14462403f11..17dca4ef2438b51 100644 --- a/files/en-us/mdn/tools/unsupported_get_api/index.md +++ b/files/en-us/mdn/tools/unsupported_get_api/index.md @@ -20,11 +20,11 @@ MDN's platform, [Yari](https://github.com/mdn/yari), doesn't provide a supported Given the URL for a particular MDN article, by making an HTTP GET request to the corresponding URL with `/index.json` appended, you can retrieve associated JSON data. -For example, for the MDN article at: +For example, for the following MDN article: [https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch](/en-US/docs/Web/API/Fetch_API/Using_Fetch) -...you can retrieve its associated JSON data at: +You can retrieve its associated JSON data at: [https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch/index.json](/en-US/docs/Web/API/Fetch_API/Using_Fetch/index.json) diff --git a/files/en-us/mozilla/add-ons/webextensions/api/browsingdata/remove/index.md b/files/en-us/mozilla/add-ons/webextensions/api/browsingdata/remove/index.md index c3fd65c4cbc20a9..0a04f8779b5d4b8 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/browsingdata/remove/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/browsingdata/remove/index.md @@ -36,7 +36,7 @@ let removing = browser.browsingData.remove( - `removalOptions` - : `object`. A {{WebExtAPIRef("browsingData.RemovalOptions")}} object, which may be used to control how far back in time to remove data, and whether to remove data from hosted web apps and extensions, or just normal web pages. - `dataTypes` - - : `object`. A {{WebExtAPIRef("browsingData.DataTypeSet")}} object, describing the types of data to remove (e.g. history, downloads, ...). + - : `object`. A {{WebExtAPIRef("browsingData.DataTypeSet")}} object, describing the types of data to remove (e.g. history, downloads, …). ### Return value diff --git a/files/en-us/mozilla/add-ons/webextensions/api/browsingdata/settings/index.md b/files/en-us/mozilla/add-ons/webextensions/api/browsingdata/settings/index.md index 697c417561acf98..b85edd359f2446a 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/browsingdata/settings/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/browsingdata/settings/index.md @@ -14,7 +14,7 @@ browser-compat: webextensions.api.browsingData.settings --- {{AddonSidebar()}} -Browsers have a built-in "Clear History" feature, which enables the user to clear various types of browsing data. This has a UI that enables the user to select what type of data to remove (e.g. history, downloads, ...) and how far back in time to remove data. +Browsers have a built-in "Clear History" feature, which enables the user to clear various types of browsing data. This has a UI that enables the user to select what type of data to remove (e.g. history, downloads, …) and how far back in time to remove data. This function returns the current value of these settings. diff --git a/files/en-us/mozilla/add-ons/webextensions/api/pkcs11/index.md b/files/en-us/mozilla/add-ons/webextensions/api/pkcs11/index.md index 314373df45e9336..708ad3b7c7ba02a 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/pkcs11/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/pkcs11/index.md @@ -26,7 +26,7 @@ Perform the following steps: 1. Save the PKCS #11 module to a permanent location on your local computer 2. Select **Tools > Options** or select the **Firefox menu** and then **Options** 3. Once the Options page opens, select **Privacy & Security** -4. Scroll down to the bottom of the page and under **Certificates** click or tap on **Security Devices... +4. Scroll down to the bottom of the page and under **Certificates** click or tap on **Security Devices… ![](device_manager.png)** 5. Click or tap the **Load** button ![](load_device_driver.png) @@ -34,7 +34,7 @@ Perform the following steps: > **Warning:** Be careful about using international characters as there is currently a bug in Firefox where international characters may cause problems. -7. Choose **Browse...** to find the location of the PKCS #11 module on your local computer, and then click or tap **OK** to confirm. +7. Choose **Browse…** to find the location of the PKCS #11 module on your local computer, and then click or tap **OK** to confirm. ## Provisioning PKCS #11 modules diff --git a/files/en-us/mozilla/add-ons/webextensions/api/userscripts/working_with_userscripts/index.md b/files/en-us/mozilla/add-ons/webextensions/api/userscripts/working_with_userscripts/index.md index 556376339f3920f..0d9f8eb73d1013b 100644 --- a/files/en-us/mozilla/add-ons/webextensions/api/userscripts/working_with_userscripts/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/api/userscripts/working_with_userscripts/index.md @@ -36,7 +36,7 @@ The "api_script" property indicates the path to the JavaScript file that contain Once you have downloaded the example: -Navigate to about:debugging, click on **Load Temporary Add-on...** and double-click on the extension's manifest. +Navigate to about:debugging, click on **Load Temporary Add-on…** and double-click on the extension's manifest. The default code included with the example allows you to load a `userScript` which will "eat" the content of pages matching the Hosts entry. Make any changes you want to make before clicking the **Register script** button at the bottom of the panel. diff --git a/files/en-us/mozilla/add-ons/webextensions/manifest.json/content_scripts/index.md b/files/en-us/mozilla/add-ons/webextensions/manifest.json/content_scripts/index.md index 7de2450ba6c9568..7ca264059d1ad44 100644 --- a/files/en-us/mozilla/add-ons/webextensions/manifest.json/content_scripts/index.md +++ b/files/en-us/mozilla/add-ons/webextensions/manifest.json/content_scripts/index.md @@ -163,12 +163,12 @@ Details of all the keys you can include are given in the table below.

Files are injected in the order given. This means that, for example, if you include jQuery here followed by another content script, like - this... + this: 

 "js": ["jquery.js", "my-content-script.js"]
-

...then "my-content-script.js" can use jQuery.

+

Then "my-content-script.js" can use jQuery.

The files are injected after any files in css _Edit List..._) is now more intuitive and simpler to use ({{bug(1487857)}}). +- [Responsive design mode](https://firefox-source-docs.mozilla.org/devtools-user/responsive_design_mode/index.html) has been redesigned — the _Device Settings_ dialog (device selection menu > _Edit List…_) is now more intuitive and simpler to use ({{bug(1487857)}}). #### Removals diff --git a/files/en-us/related/criteria_for_inclusion/index.md b/files/en-us/related/criteria_for_inclusion/index.md index 48ecca72a59d9ba..c3cb3466231c409 100644 --- a/files/en-us/related/criteria_for_inclusion/index.md +++ b/files/en-us/related/criteria_for_inclusion/index.md @@ -25,7 +25,7 @@ Therefore, if you want to consider a non-web standard technology for inclusion i ## The criteria -To be applicable for consideration, technologies should... +To be applicable for consideration, technologies should… ### Be open and not proprietary diff --git a/files/en-us/related/project_guidelines/index.md b/files/en-us/related/project_guidelines/index.md index 07de6b8763f66e2..9d362ae832da02a 100644 --- a/files/en-us/related/project_guidelines/index.md +++ b/files/en-us/related/project_guidelines/index.md @@ -35,7 +35,7 @@ Once your team is assembled, you'll need to get them all to [create MDN accounts Write down a plan for the work — what needs to be done, and when? What milestones do you need to reach so that progress is healthy? If the project is large, you should consider getting one of your team members to be a project manager for the project, and using a project tracking tool like [Trello](https://trello.com/). You should also consider writing a sub-project plan for an initial release that encompasses the minimum set of documentation that is useful to publish (a _minimum viable product_), do that first, and then follow up with further additions later. -If the documentation resource is small, then this probably isn't so critical, but you still need to keep a record of what has been done and what hasn't, what stage each part of the documentation is at (e.g. not started, in progress, draft written, reviewed, done...), and who is working on what. +If the documentation resource is small, then this probably isn't so critical, but you still need to keep a record of what has been done and what hasn't, what stage each part of the documentation is at (e.g. not started, in progress, draft written, reviewed, done…), and who is working on what. ## Guidelines and standards @@ -43,7 +43,7 @@ There are [guidelines available on MDN](/en-US/docs/MDN/Guidelines) that state h Since this is a project in its own right, you may have additional guidelines on language or code styles that you expect to be followed. Feel free to keep a record of these, and even host them on a page inside your own project pages. -In terms of standards, you are expected to maintain a reasonable level of quality for your documentation to stay on MDN. Your MDN rep will work with you on this to make you clear on what is expected. It is a good idea to produce a prototype showing what each type of page in your documentation should look like (e.g. an element or method reference page, a code example...) so that people have a template to follow. +In terms of standards, you are expected to maintain a reasonable level of quality for your documentation to stay on MDN. Your MDN rep will work with you on this to make you clear on what is expected. It is a good idea to produce a prototype showing what each type of page in your documentation should look like (e.g. an element or method reference page, a code example…) so that people have a template to follow. > **Note:** MDN is primarily an English site (en-US). The primary language for your resource should be in US English. If this really doesn't make sense for your project (e.g. it might be for a tool usable in a specific non-English locale), then talk to us about it, and we'll see how we can accommodate this. diff --git a/files/en-us/web/api/abstractrange/index.md b/files/en-us/web/api/abstractrange/index.md index 1517464eb8c140a..76fe8a718a6fdae 100644 --- a/files/en-us/web/api/abstractrange/index.md +++ b/files/en-us/web/api/abstractrange/index.md @@ -108,7 +108,7 @@ pRange.selectNodeContents(document.querySelector("#entry1 p")); Since we wish to select the entire contents of the `

` element, including its descendants, this works perfectly. -If we wish to instead copy the text "An interesting thing..." from the {{HTMLElement("section")}}'s heading (an {{HTMLElement("Heading_Elements", "h2")}} element) through the end of the letters "ve" in the {{HTMLElement("em")}} within the paragraph below it, the following code would work: +If we wish to instead copy the text "An interesting thing…" from the {{HTMLElement("section")}}'s heading (an {{HTMLElement("Heading_Elements", "h2")}} element) through the end of the letters "ve" in the {{HTMLElement("em")}} within the paragraph below it, the following code would work: ```html let r = document.createRange(); @@ -129,7 +129,7 @@ In this example, the start of the specified range is found within the text node The range's end is located below the {{HTMLElement("p")}} element, so that will be needed within the new fragment. So will the text node containing the word "A", since that's included in the range. Finally, an `` and a text node below it will be added below the `

` as well. -The contents of the text nodes are then determined by the offsets into those text nodes given when calling {{domxref("Range.setStart", "setStart()")}} and {{domxref("Range.setEnd", "setEnd()")}}. Given the offset of 11 into the heading's text, that node will contain "An interesting thing...". Similarly, the last text node will contain "ve", given the request for the first two characters of the ending node. +The contents of the text nodes are then determined by the offsets into those text nodes given when calling {{domxref("Range.setStart", "setStart()")}} and {{domxref("Range.setEnd", "setEnd()")}}. Given the offset of 11 into the heading's text, that node will contain "An interesting thing…". Similarly, the last text node will contain "ve", given the request for the first two characters of the ending node. The resulting document fragment looks like this: diff --git a/files/en-us/web/api/css_painting_api/guide/index.md b/files/en-us/web/api/css_painting_api/guide/index.md index d54fbfca03c79ae..a00478a8682b70c 100644 --- a/files/en-us/web/api/css_painting_api/guide/index.md +++ b/files/en-us/web/api/css_painting_api/guide/index.md @@ -447,7 +447,7 @@ When we `get` our list of argument values, we can ask specifically for a `']; } ``` -Now we can access the type and value properties, meaning we can get the number of pixels and a number type right out of the box. (Admittedly, `ctx.lineWidth` takes a float as a value rather than a value with length units, but for example's sake...) +Now we can access the type and value properties, meaning we can get the number of pixels and a number type right out of the box. (Admittedly, `ctx.lineWidth` takes a float as a value rather than a value with length units, but for example's sake…) ```js paint(ctx, size, props, args) { diff --git a/files/en-us/web/api/document/requeststorageaccess/index.md b/files/en-us/web/api/document/requeststorageaccess/index.md index cc32a8c99ab5392..89e2a8d4e70f522 100644 --- a/files/en-us/web/api/document/requeststorageaccess/index.md +++ b/files/en-us/web/api/document/requeststorageaccess/index.md @@ -70,7 +70,7 @@ storage access to fewer sites than the maximum and has been interacted with as a - Not persisted to disk (e.g. will not persist if the browser crashes). - Reset after 24 hours in the case of a long-running browser session. -...equal or more sites than the maximum or has not been interacted with as a first party in the last 30 days:: +When equal or more sites than the maximum or has not been interacted with as a first party in the last 30 days: - The user is prompted - If the user clicks "Allow" or "Allow on any site" the request is resolved. diff --git a/files/en-us/web/api/document/xmlencoding/index.md b/files/en-us/web/api/document/xmlencoding/index.md index 1142d805aa3035b..27a631675c4b1e6 100644 --- a/files/en-us/web/api/document/xmlencoding/index.md +++ b/files/en-us/web/api/document/xmlencoding/index.md @@ -17,13 +17,13 @@ Returns the encoding as determined by the XML declaration. Should be `null` if u > **Warning:** Do not use this attribute; it has been removed from the DOM Level 4 specification and is no longer supported in Gecko 10.0 {{ geckoRelease("10.0") }}. -If the XML Declaration states: +If the XML Declaration states following: ```xml ``` -...the result should be "UTF-16". +Then the result should be "UTF-16". However, Firefox 3.0 includes information on endianness (e.g., UTF-16BE for big endian encoding), and while this extra information is removed as of Firefox 3.1b3, Firefox 3.1b3 is still consulting the file's encoding, rather than the XML Declaration as the spec defines it ("An attribute specifying, _as part of the XML declaration_, the encoding of this document."). diff --git a/files/en-us/web/api/fontfaceset/loading_event/index.md b/files/en-us/web/api/fontfaceset/loading_event/index.md index 69cf17f0bd6ddde..043f8167945c89b 100644 --- a/files/en-us/web/api/fontfaceset/loading_event/index.md +++ b/files/en-us/web/api/fontfaceset/loading_event/index.md @@ -26,7 +26,7 @@ onloading = event => { }; ## Example -In the following example, when the font `Ephesis` starts to load, "Font is loading..." is printed to the console. +In the following example, when the font `Ephesis` starts to load, "Font is loading…" is printed to the console. ```js document.fonts.onloading = () => { diff --git a/files/en-us/web/api/htmlmediaelement/autoplay/index.md b/files/en-us/web/api/htmlmediaelement/autoplay/index.md index c70ad0652a67211..367daaba778cef5 100644 --- a/files/en-us/web/api/htmlmediaelement/autoplay/index.md +++ b/files/en-us/web/api/htmlmediaelement/autoplay/index.md @@ -49,8 +49,6 @@ interruption. ## Examples -... - ```html 

 "js": ["jquery.js", "my-content-script.js"]
-

Then "my-content-script.js" can use jQuery.

+

Then, "my-content-script.js" can use jQuery.

The files are injected after any files in css **Warning:** Do not use this attribute; it has been removed from the DOM Level 4 specification and is no longer supported in Gecko 10.0 {{ geckoRelease("10.0") }}. -If the XML Declaration states following: +Consider the following XML Declaration: ```xml ``` -Then the result should be "UTF-16". +Then, the result should be "UTF-16". However, Firefox 3.0 includes information on endianness (e.g., UTF-16BE for big endian encoding), and while this extra information is removed as of Firefox 3.1b3, Firefox 3.1b3 is still consulting the file's encoding, rather than the XML Declaration as the spec defines it ("An attribute specifying, _as part of the XML declaration_, the encoding of this document."). diff --git a/files/en-us/web/api/paymentresponse/retry/index.md b/files/en-us/web/api/paymentresponse/retry/index.md index d27bf6fcd4fd570..5d8cfdb4f69d90a 100644 --- a/files/en-us/web/api/paymentresponse/retry/index.md +++ b/files/en-us/web/api/paymentresponse/retry/index.md @@ -60,7 +60,7 @@ concept, in outline form, is: (`new` {{domxref("PaymentRequest.PaymentRequest", "PaymentRequest()")}}) 2. Display the payment request ({{domxref("PaymentRequest.show()")}} 3. If `show()` resolves, the returned {{domxref("PaymentResponse")}} - describes the requested payment and the options chosen by the user. Continue by… + describes the requested payment and the options chosen by the user. Continue with the following steps: 1. Validate the returned response; if there are any fields whose values are not acceptable, call the response's {{domxref("PaymentResponse.complete", diff --git a/files/en-us/web/api/rtcremoteoutboundrtpstreamstats/localid/index.md b/files/en-us/web/api/rtcremoteoutboundrtpstreamstats/localid/index.md index 6e5e6eba7c236f2..71aad4526676e66 100644 --- a/files/en-us/web/api/rtcremoteoutboundrtpstreamstats/localid/index.md +++ b/files/en-us/web/api/rtcremoteoutboundrtpstreamstats/localid/index.md @@ -59,7 +59,7 @@ example on Glitch. In this example, we have a pair of functions: the first, `networkTestStart()`, captures an initial report, and the second, `networkTestStop()`, captures a second report. -Then the second function, uses the two reports to output some information about the network conditions. +The second function uses the two reports to output some information about the network conditions. ### networkTestStart() diff --git a/files/en-us/web/api/webvtt_api/index.md b/files/en-us/web/api/webvtt_api/index.md index 79ba57217e930b1..41dbd249ce15e44 100644 --- a/files/en-us/web/api/webvtt_api/index.md +++ b/files/en-us/web/api/webvtt_api/index.md @@ -277,7 +277,7 @@ Some time ago in a place rather distant.... ### Cue identifier -The identifier is a name that identifies the cue. It can be used to reference the cue from a script. It must not contain a newline and cannot contain the string "`-->"`. It must end with a single newline. They do not have to be unique, although it is common to number them (e.g., 1, 2, 3, …). +The identifier is a name that identifies the cue. It can be used to reference the cue from a script. It must not contain a newline and cannot contain the string "`-->"`. It must end with a single new line. They do not have to be unique, although it is common to number them (e.g., 1, 2, 3). ##### Example 8 - Cue identifier from Example 7 From deb243278bc73ffaf8293846af3c289fd79ad53f Mon Sep 17 00:00:00 2001 From: Onkar Ruikar <87750369+OnkarRuikar@users.noreply.github.com> Date: Mon, 11 Jul 2022 13:26:51 +0530 Subject: [PATCH 3/3] Update files/en-us/mdn/structures/page_types/api_landing_page_template/index.md Co-authored-by: Jean-Yves Perrier --- .../structures/page_types/api_landing_page_template/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/mdn/structures/page_types/api_landing_page_template/index.md b/files/en-us/mdn/structures/page_types/api_landing_page_template/index.md index 440d66202a4dbc4..670b16732f8ae16 100644 --- a/files/en-us/mdn/structures/page_types/api_landing_page_template/index.md +++ b/files/en-us/mdn/structures/page_types/api_landing_page_template/index.md @@ -109,7 +109,7 @@ In this section, describe the API's purpose and usage cases in a bit more detail What problems does it solve? What concepts does it involve? How do you use it, from a high level perspective? Don't go into a lot of detail in this section, and don't include code examples. -If there are a lot of concepts to explain around this API, you should explain them in a separate "Fundamentals …" or "Concepts…" article (e.g. [Fundamentals of WebXR](/en-US/docs/Web/API/WebXR_Device_API/Fundamentals)). +If there are a lot of concepts to explain around this API, you should explain them in a separate "Fundamentals" or "Concepts" article (e.g. [Fundamentals of WebXR](/en-US/docs/Web/API/WebXR_Device_API/Fundamentals)). For a practical usage guide with code examples, you should include a "Usage…" article in your API docs (e.g. [Using the WebVR API](/en-US/docs/Web/API/WebVR_API/Using_the_WebVR_API)). To help improve content discoverability and {{Glossary("SEO")}}, keep the following tips in mind: