Update redirected URLs (part 41) (#15842)

* Update redirected URLs * Apply suggestions from code review * Update files/en-us/web/javascript/a_re-introduction_to_javascript/index.md Co-authored-by: Jean-Yves Perrier <[email protected]> Co-authored-by: Jean-Yves Perrier <[email protected]>
mdn · May 10, 2022 · f435092 · f435092
1 parent 23901d9
commit f435092
Show file tree

Hide file tree

Showing 33 changed files with 41 additions and 41 deletions.
diff --git a/.../web/guide/audio_and_video_delivery/live_streaming_web_audio_and_video/index.md b/.../web/guide/audio_and_video_delivery/live_streaming_web_audio_and_video/index.md
@@ -145,7 +145,7 @@ In order to stream live audio and video, you will need to run specific streaming
 
 [GStreamer](https://gstreamer.freedesktop.org/) is an open source cross-platform multimedia framework that allows you to create a variety of media-handling components, including streaming components. Through its plugin system, GStreamer provides support for more than a hundred codecs (including MPEG-1, MPEG-2, MPEG-4, H.261, H.263, H.264, RealVideo, MP3, WMV, and FLV.)
 
-GStreamer plugins such as [souphttpclientsink](https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good-plugins/html/gst-plugins-good-plugins-plugin-soup.html) and [shout2send](https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good/html/gst-plugins-good-plugins-shout2send.html) exist to stream media over HTTP or you can also integrate with Python's Twisted framework.
+GStreamer plugins such as [souphttpclientsink](https://gstreamer.freedesktop.org/documentation/soup/souphttpclientsink.html?gi-language=c) and [shout2send](https://gstreamer.freedesktop.org/data/doc/gstreamer/head/gst-plugins-good/html/gst-plugins-good-plugins-shout2send.html) exist to stream media over HTTP or you can also integrate with Python's Twisted framework.
 
 For RTMP transfer you can use the [Nginx RTMP Module](https://github.com/arut/nginx-rtmp-module).
 
@@ -177,7 +177,7 @@ Although you can install software like GStreamer, SHOUTcast and Icecast you will
 - [DASH Reference Client](https://dashif.org/reference/players/javascript/1.0.0/index.html)
 - [Dynamic Streaming over HTTP](https://en.wikipedia.org/wiki/Dynamic_Adaptive_Streaming_over_HTTP)
 - [The State of MPEG-DASH Deployment](https://www.streamingmediaglobal.com/Articles/Editorial/Featured-Articles/The-State-of-MPEG-DASH-Deployment-96144.aspx)
-- [Look, no plugins: Live streaming to the browser using Media Source Extensions and MPEG-DASH](https://www.bbc.co.uk/rd/blog/2014/03/media-source-extensions)
+- [Look, no plugins: Live streaming to the browser using Media Source Extensions and MPEG-DASH](https://www.bbc.co.uk/rd/blog/2014-03-media-source-extensions)
 - [Media Source Extensions (W3C)](https://w3c.github.io/media-source/)
 - [Icecast](https://en.wikipedia.org/wiki/Icecast)
 - [SHOUTcast](https://en.wikipedia.org/wiki/Shoutcast)

diff --git a/files/en-us/web/guide/introduction_to_web_development/index.md b/files/en-us/web/guide/introduction_to_web_development/index.md
@@ -39,14 +39,14 @@ For another (overlapping) set of links to learning resources, see the [MDN Learn
 - [Getting started with JavaScript](/en-US/docs/Learn/Getting_started_with_the_web/JavaScript_basics) — what is JavaScript and how can it help you?
 - [JavaScript reference guide](/en-US/docs/Web/JavaScript/Guide) — a comprehensive, regularly updated guide to JavaScript for all levels of learning from beginner to advanced.
 - [Crockford on JavaScript](https://www.youtube.com/playlist?list=PL7664379246A246CB) — an in-depth video series on the JavaScript language.
-- [Eloquent JavaScript](https://eloquentjavascript.net/contents.html) — a comprehensive guide to intermediate and advanced JavaScript methodologies
+- [Eloquent JavaScript](https://eloquentjavascript.net/) — a comprehensive guide to intermediate and advanced JavaScript methodologies
 
 #### Intermediate
 
 - [A re-introduction to JavaScript](/en-US/docs/Web/JavaScript/A_re-introduction_to_JavaScript) — a recap on the JavaScript programming language aimed at intermediate-level developers
 - [Essential JavaScript design patterns](https://addyosmani.com/resources/essentialjsdesignpatterns/book/) — an introduction to essential JavaScript design patterns
 - [Introduction to object-oriented JavaScript](/en-US/docs/Learn/JavaScript/Objects) — learn about the JavaScript object model.
-- [Christian Heilmann's JavaScript best practices](https://dev.opera.com/articles/view/javascript-best-practices/) — learn about some of the obvious and (not so) obvious best practices when writing JavaScript.
+- [Christian Heilmann's JavaScript best practices](https://dev.opera.com/articles/javascript-best-practices/) — learn about some of the obvious and (not so) obvious best practices when writing JavaScript.
 
 #### Advanced
 

diff --git a/files/en-us/web/guide/mobile/a_hybrid_approach/index.md b/files/en-us/web/guide/mobile/a_hybrid_approach/index.md
@@ -18,7 +18,7 @@ Luckily, we aren't technically constrained to using client-side techniques here:
 
 Using user-agent detection specifically for content and not layout also allows you to have a single URL for each piece of content, so that the content can adapt its layout to the user's browser. This is generally thought to be [a good thing](https://www.w3.org/TR/mobile-bp/#OneWeb "W3C One Web Recommendation"). Instead of maintaining two completely different sites, we redirect users to pages for the content they care about. And since the design is responsive, you know that each page looks as good as possible on the user's screen.
 
-We can also address some of the performance problems with responsive design by incorporating server-side techniques. For example, an often-criticized point about responsive web design is that full-resolution images are sent to all devices, including phones that show the images scaled down anyway. [One such technique](http://wurfl.sourceforge.net/utilities/imageserver.php) for dealing with this issue uses server-side user-agent detection along with the [WURFL](http://wurfl.sourceforge.net/) device capability library to send a properly sized image for the user's device. A [range](http://imgble.com/ "IMGBLE") of [products](http://www.sencha.com/products/io/ "Sencha IO") are also emerging which provide this as a service. Of course, this technique suffers from all the downsides associated with user-agent detection. But even if it does not work, it is no worse with respect to performance than only using [fluid images](https://unstoppablerobotninja.com/entry/fluid-images/).
+We can also address some of the performance problems with responsive design by incorporating server-side techniques. For example, an often-criticized point about responsive web design is that full-resolution images are sent to all devices, including phones that show the images scaled down anyway. [One such technique](http://wurfl.sourceforge.net/utilities/imageserver.php) for dealing with this issue uses server-side user-agent detection along with the [WURFL](http://wurfl.sourceforge.net/) device capability library to send a properly sized image for the user's device. A [range](http://imgble.com/ "IMGBLE") of [products](https://www.sencha.com/platform/ "Sencha IO") are also emerging which provide this as a service. Of course, this technique suffers from all the downsides associated with user-agent detection. But even if it does not work, it is no worse with respect to performance than only using [fluid images](https://unstoppablerobotninja.com/entry/fluid-images/).
 
 By combining the techniques listed above, we can get a mobile web development strategy that is both more flexible than pure separate sites and has better performance than pure responsive design.
 

diff --git a/files/en-us/web/guide/mobile/separate_sites/index.md b/files/en-us/web/guide/mobile/separate_sites/index.md
@@ -21,7 +21,7 @@ Even more important than that, though, is the fact that user-agent detection is
 
 ## When it is right to choose this option
 
-![](sumo_screenshot.png)Firstly, if your target audience includes users on older or low-end [feature phones](https://www.cnet.com/8301-17918_1-10461614-85.html "Feature Phones Definition"), it is worth noting that you may need to employ this strategy [to some degree](https://www.passani.it/gap/#adaptation "Mobile Adaptation") no matter what. This is because the default browsers on some feature-phones do not support the same markup that you would use to code a website targeted at the desktop, but instead understand formats like [XHTML-MP](https://en.wikipedia.org/wiki/XHTML_Mobile_Profile) or the older [WML](https://en.wikipedia.org/wiki/Wireless_Markup_Language).
+![](sumo_screenshot.png)Firstly, if your target audience includes users on older or low-end [feature phones](https://www.cnet.com/tech/mobile/the-411-feature-phones-vs-smartphones/ "Feature Phones Definition"), it is worth noting that you may need to employ this strategy [to some degree](https://www.passani.it/gap/#adaptation "Mobile Adaptation") no matter what. This is because the default browsers on some feature-phones do not support the same markup that you would use to code a website targeted at the desktop, but instead understand formats like [XHTML-MP](https://en.wikipedia.org/wiki/XHTML_Mobile_Profile) or the older [WML](https://en.wikipedia.org/wiki/Wireless_Markup_Language).
 
 This factor aside, there is one case where this strategy really shines over other methods. If the functionality you would like to provide to your users on mobile devices is extremely different from that on a desktop, then using separate sites is likely to be the [most practical choice](https://tripleodeon.com/2010/10/not-a-mobile-web-merely-a-320px-wide-one/). This is because you have the option of sending completely separate HTML, JavaScript, and CSS to phones and PCs.
 

diff --git a/files/en-us/web/html/attributes/rel/index.md b/files/en-us/web/html/attributes/rel/index.md
@@ -113,7 +113,7 @@ The `rel` attribute has no default value. If the attribute is omitted or if none
     > **Note:** Prior to Firefox 83 the [crossorigin](/en-US/docs/Web/HTML/Attributes/crossorigin) attribute was not supported for `rel="icon"` there is also [an open issue for Chrome](https://bugs.chromium.org/p/chromium/issues/detail?id=1121645).
 
     > **Note:** Apple's iOS does not use this link type, nor the [`sizes`](sizes) attribute, like others mobile browsers do, to select a webpage icon for Web Clip or a start-up placeholder.
-    > Instead it uses the non-standard [`apple-touch-icon`](https://developer.apple.com/library/content/documentation/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.html#//apple_ref/doc/uid/TP40002051-CH3-SW4) and [`apple-touch-startup-image`](https://developer.apple.com/library/content/documentation/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.html#//apple_ref/doc/uid/TP40002051-CH3-SW6) respectively.
+    > Instead it uses the non-standard [`apple-touch-icon`](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.html#//apple_ref/doc/uid/TP40002051-CH3-SW4) and [`apple-touch-startup-image`](https://developer.apple.com/library/archive/documentation/AppleApplications/Reference/SafariWebContent/ConfiguringWebApplications/ConfiguringWebApplications.html#//apple_ref/doc/uid/TP40002051-CH3-SW6) respectively.
 
     > **Note:** The `shortcut` link type is often seen before `icon`, but this link type is non-conforming, ignored and **web authors must not use it anymore**.
 

diff --git a/files/en-us/web/html/element/a/index.md b/files/en-us/web/html/element/a/index.md
@@ -483,7 +483,7 @@ Text-only links in prose content are exempt from this requirement, but it's stil
 
 - [Understanding Success Criterion 2.5.5: Target Size](https://www.w3.org/WAI/WCAG21/Understanding/target-size.html)
 - [Target Size and 2.5.5](https://adrianroselli.com/2019/06/target-size-and-2-5-5.html)
-- [Quick test: Large touch targets](https://www.a11yproject.com/posts/2018-11-21-large-touch-targets/)
+- [Quick test: Large touch targets](https://www.a11yproject.com/posts/large-touch-targets/)
 
 #### Proximity
 

diff --git a/files/en-us/web/html/element/button/index.md b/files/en-us/web/html/element/button/index.md
@@ -246,7 +246,7 @@ Firefox will add a small dotted border on a focused button. This border is decla
 
 If overridden, it is important to **ensure that the state change when focus is moved to the button is high enough** that people experiencing low vision conditions will be able to perceive it.
 
-Color contrast ratio is determined by comparing the luminosity of the button text and background color values compared to the background the button is placed on. In order to meet current [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/intro/wcag), a ratio of 4.5:1 is required for text content and 3:1 for large text. (Large text is defined as 18.66px and {{cssxref("font-weight", "bold")}} or larger, or 24px or larger.)
+Color contrast ratio is determined by comparing the luminosity of the button text and background color values compared to the background the button is placed on. In order to meet current [Web Content Accessibility Guidelines (WCAG)](https://www.w3.org/WAI/standards-guidelines/wcag/), a ratio of 4.5:1 is required for text content and 3:1 for large text. (Large text is defined as 18.66px and {{cssxref("font-weight", "bold")}} or larger, or 24px or larger.)
 
 - [WebAIM: Color Contrast Checker](https://webaim.org/resources/contrastchecker/)
 - [MDN Understanding WCAG, Guideline 1.4 explanations](/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable#guideline_1.4_make_it_easier_for_users_to_see_and_hear_content_including_separating_foreground_from_background)

diff --git a/files/en-us/web/html/element/input/index.md b/files/en-us/web/html/element/input/index.md
@@ -1374,7 +1374,7 @@ Interactive elements such as form input should provide an area large enough that
 
 - [Understanding Success Criterion 2.5.5: Target Size | W3C Understanding WCAG 2.1](https://www.w3.org/WAI/WCAG21/Understanding/target-size.html)
 - [Target Size and 2.5.5 | Adrian Roselli](https://adrianroselli.com/2019/06/target-size-and-2-5-5.html)
-- [Quick test: Large touch targets - The A11Y Project](https://www.a11yproject.com/posts/2018-11-21-large-touch-targets/)
+- [Quick test: Large touch targets - The A11Y Project](https://www.a11yproject.com/posts/large-touch-targets/)
 
 ## Specifications
 

diff --git a/files/en-us/web/html/element/input/time/index.md b/files/en-us/web/html/element/input/time/index.md
@@ -288,7 +288,7 @@ The result here is that:
 
 #### Making min and max cross midnight
 
-By setting a {{htmlattrxref("min", "input")}} attribute greater than the {{htmlattrxref("max", "input")}} attribute, the valid time range will wrap around midnight to produce a valid time range which crosses midnight. This functionality is not supported by any other input types. While this feature is [in the HTML spec](https://html.spec.whatwg.org/C/#has-a-reversed-range), it is not yet universally supported. Chrome-based browsers support it starting in version 82 and Firefox added it in version 76. Safari as of version 14.1 does not support this. Be prepared for this situation to arise:
+By setting a {{htmlattrxref("min", "input")}} attribute greater than the {{htmlattrxref("max", "input")}} attribute, the valid time range will wrap around midnight to produce a valid time range which crosses midnight. This functionality is not supported by any other input types. While this feature is [in the HTML spec](https://html.spec.whatwg.org/multipage/input.html#has-a-reversed-range), it is not yet universally supported. Chrome-based browsers support it starting in version 82 and Firefox added it in version 76. Safari as of version 14.1 does not support this. Be prepared for this situation to arise:
 
 ```js
 const input = document.createElement('input');

diff --git a/files/en-us/web/html/element/wbr/index.md b/files/en-us/web/html/element/wbr/index.md
@@ -86,7 +86,7 @@ This element was first implemented in Internet Explorer 5.5 and was officially d
 
 ## Example
 
-_[The Yahoo Style Guide](https://web.archive.org/web/20121014054923/http://styleguide.yahoo.com/)_ recommends [breaking a URL _before_ punctuation](https://web.archive.org/web/20121014054923/http://styleguide.yahoo.com/editing/treat-abbreviations-capitalization-and-titles-consistently/website-names-and-addresses), to avoid leaving a punctuation mark at the end of the line, which the reader might mistake for the end of the URL.
+_[The Yahoo Style Guide](https://web.archive.org/web/20121014054923/http://styleguide.yahoo.com/)_ recommends [breaking a URL _before_ punctuation](https://web.archive.org/web/20121105171040/http://styleguide.yahoo.com/editing/treat-abbreviations-capitalization-and-titles-consistently/website-names-and-addresses), to avoid leaving a punctuation mark at the end of the line, which the reader might mistake for the end of the URL.
 
 ```html
 <p>http://this<wbr>.is<wbr>.a<wbr>.really<wbr>.long<wbr>.example<wbr>.com/With<wbr>/deeper<wbr>/level<wbr>/pages<wbr>/deeper<wbr>/level<wbr>/pages<wbr>/deeper<wbr>/level<wbr>/pages<wbr>/deeper<wbr>/level<wbr>/pages<wbr>/deeper<wbr>/level<wbr>/pages</p>

diff --git a/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md b/files/en-us/web/http/basics_of_http/choosing_between_www_and_non-www_urls/index.md
@@ -57,7 +57,7 @@ With these techniques, you can configure your server to respond correctly for bo
 
 ## Deciding the case
 
-This is a very subjective topic it could be considered a [bikeshedding](https://bikeshed.com/) issue. If you wish to read deeper, please see some of the [many](https://www.netlify.com/blog/2017/02/28/to-www-or-not-www/) [articles](https://www.wpbeginner.com/beginners-guide/www-vs-non-www-which-is-better-for-wordpress-seo/) on the subject.
+This is a very subjective topic it could be considered a [bikeshedding](https://bikeshed.com/) issue. If you wish to read deeper, please see some of the [many](https://www.netlify.com/blog/2020/03/26/how-to-set-up-netlify-dns-custom-domains-cname-and-a-records/#options-for-bare-domains) [articles](https://www.wpbeginner.com/beginners-guide/www-vs-non-www-which-is-better-for-wordpress-seo/) on the subject.
 
 ## See also
 

diff --git a/files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.md b/files/en-us/web/http/headers/feature-policy/screen-wake-lock/index.md
@@ -47,4 +47,4 @@ Default allow list for `screen-wake-lock` is `'self'`.
 - {{HTTPHeader('Feature-Policy')}} header
 - [Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy)
 - [Using Feature Policy](/en-US/docs/Web/HTTP/Feature_Policy/Using_Feature_Policy)
-- [Default value of the allow list](https://www.w3.org/TR/wake-lock/#wake-locks)
+- [Default value of the allow list](https://www.w3.org/TR/screen-wake-lock/#wake-locks)
diff --git a/files/en-us/web/http/headers/index.md b/files/en-us/web/http/headers/index.md
@@ -13,7 +13,7 @@ tags:
 
 **HTTP headers** let the client and the server pass additional information with an HTTP request or response. An HTTP header consists of its case-insensitive name followed by a colon (`:`), then by its value. {{Glossary("Whitespace")}} before the value is ignored.
 
-Custom proprietary headers have historically been used with an `X-` prefix, but this convention was deprecated in June 2012 because of the inconveniences it caused when nonstandard fields became standard in [RFC 6648](https://datatracker.ietf.org/doc/html/rfc6648); others are listed in an [IANA registry](https://www.iana.org/assignments/message-headers/perm-headers.html), whose original content was defined in [RFC 4229](https://datatracker.ietf.org/doc/html/rfc4229). IANA also maintains a [registry of proposed new HTTP headers](https://www.iana.org/assignments/message-headers/prov-headers.html).
+Custom proprietary headers have historically been used with an `X-` prefix, but this convention was deprecated in June 2012 because of the inconveniences it caused when nonstandard fields became standard in [RFC 6648](https://datatracker.ietf.org/doc/html/rfc6648); others are listed in an [IANA registry](https://www.iana.org/assignments/message-headers/message-headers.xhtml#perm-headers), whose original content was defined in [RFC 4229](https://datatracker.ietf.org/doc/html/rfc4229). IANA also maintains a [registry of proposed new HTTP headers](https://www.iana.org/assignments/message-headers/message-headers.xhtml#prov-headers).
 
 Headers can be grouped according to their contexts:
 
@@ -416,5 +416,5 @@ You can help by [writing new entries](/en-US/docs/MDN/Contribute/Howto/Document_
 ## See also
 
 - [Wikipedia page on List of HTTP headers](https://en.wikipedia.org/wiki/List_of_HTTP_header_fields)
-- [IANA registry](https://www.iana.org/assignments/message-headers/perm-headers.html)
+- [IANA registry](https://www.iana.org/assignments/message-headers/message-headers.xhtml#perm-headers)
 - [HTTP Working Group](https://httpwg.org/specs/)