NOJIRA: update more redirected links

src/_includes/layouts/base.njk

@@ -171,7 +171,7 @@
 
                     <footer class="row infusion-docs-footer">
                         <p class="infusion-docs-footerInfusion">Infusion is created by the <a href="https://fluidproject.org" target="_blank">Fluid Project</a>, a project of the <a href="https://idrc.ocadu.ca" target="_blank">Inclusive Design Research Centre</a> at <a href="https://www.ocadu.ca" target="_blank">OCAD University</a>,<br/>
-                        originally funded by a grant from <a href="https://www.mellon.org" target="_blank">The Andrew W. Mellon Foundation</a> and with continued funding support through grants from <a href="https://www.hewlett.org/" target="_blank">The William + Flora Hewlett Foundation</a>.</p>
+                        originally funded by a grant from <a href="https://www.mellon.org" target="_blank">The Andrew W. Mellon Foundation</a> and with continued funding support through grants from <a href="https://hewlett.org/" target="_blank">The William + Flora Hewlett Foundation</a>.</p>
                     </footer>
 
                 </article>

src/documents/ContextAwareness.md

@@ -44,7 +44,7 @@ of:
 ## Simple example - speech API-aware component
 
 This simple example invokes the `fluid.textToSpeech.isSupported` feature detector, which returns `true` if the current
-browser supports the [HTML5 Speech API](https://dvcs.w3.org/hg/speech-api/raw-file/tip/speechapi.html). We use the
+browser supports the [HTML5 Speech API](https://wicg.github.io/speech-api/). We use the
 `fluid.contextAware.makeChecks` function to assign the result of this feature detection to a _context_ named
 `fluid.supportsTTS`. We can then use this context to conditionally switch in an extra [grade name](ComponentGrades.md),
 `examples.myComponent.speechAware` into the `examples.myComponent` component:

src/documents/Contexts.md

@@ -27,7 +27,7 @@ Context names are derived both from particular components in the tree which have
 (ancestors) and the __*static environment*__. The static environment can be thought of as a set of
 contexts which are global to the entire application (that is, a context managed by the JavaScript
 virtual machine operated by the runtime - for example that derived from a browser frame or
-[V8 context](https://developers.google.com/v8/embed#contexts)). These names can be matched by the
+[V8 context](https://v8.dev/#contexts)). These names can be matched by the
 names appearing in curly brackets at the beginning of EL path expressions like
 `"{contextName}.furtherPath"`. Each component in the tree can give rise to a context name through
 three strategies:

src/documents/IoCTestingFramework.md

@@ -66,8 +66,8 @@ configuration defining the sequence and structure of a group of test cases which
 ### `modules`, `tests` and `sequence`
 
 The standard structure inside a `fluid.test.testCaseHolder` has an outer layer of containment, `modules`, with members
-corresponding to QUnit [modules](https://api.qunitjs.com/QUnit.module/), and within that an entry named `tests`, holding
-an array of structures corresponding to QUnit [test](https://api.qunitjs.com/QUnit.test/). In ordinary use, each element
+corresponding to QUnit [modules](https://qunitjs.com/api/QUnit/module/), and within that an entry named `tests`, holding
+an array of structures corresponding to QUnit [test](https://qunitjs.com/api/QUnit/test/). In ordinary use, each element
 `tests` then contains a member named `sequence` holding a list of [*fixture records*](#supported-fixture-records).
 
 As well as containing a flat list of fixture records, `sequence` may also contain nested arrays of such records. These

src/documents/PromisesAPI.md

@@ -9,7 +9,7 @@ requiring I/O) or fallibly. JavaScript enjoys numerous competing libraries imple
 [Bluebird](https://github.com/petkaantonov/bluebird) as well as even multiple competing promise standards, such as
 [Promises/A+](https://promisesaplus.com/) and others from [CommonJS](https://wiki.commonjs.org/wiki/Promises). Promises
 are even built into an upcoming version of the JavaScript language itself,
-[ES6](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Promise).
+[ES6](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise).
 
 Infusion required an extremely simple implementation which can evolve independently, as well as begin the process of
 merging with the general declarative facilities of [Infusion IoC](HowToUseInfusionIoC.md) and hence become invisible as

src/documents/ResourceLoader.md

@@ -109,7 +109,7 @@ it is an Object with keys described in the [section on resourceSpecs](#resources
 <tr>
     <td><code>locale</code></td>
     <td>Specifies the language code with the desired localization. Language codes are expected in a form
-    similar to <a href="https://tools.ietf.org/html/bcp47">BCP 47 tags</a> but with a "_" instead of a "-" separating
+    similar to <a href="https://www.rfc-editor.org/info/bcp47">BCP 47 tags</a> but with a "_" instead of a "-" separating
     the language code from the country code. When specified, the resource loader will add a suffix of the locale value
     to each entry defined in the <code>resources</code> and look for them at the first attempt. If any such resource is
     not located, the resource loader follows

src/documents/TextToSpeechAPI.md

@@ -4,12 +4,12 @@ category: Components
 ---
 
 The **Text To Speech** component uses [Web Speech Synthesis
-API](https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html#tts-section) to queue up and read texts.
+API](https://wicg.github.io/speech-api/#tts-section) to queue up and read texts.
 
 ## Browser Support
 
 The Text To Speech component can be used in browsers that support [Web Speech Synthesis
-API](https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html#tts-section). At the time of writing, July 26
+API](https://wicg.github.io/speech-api/#tts-section). At the time of writing, July 26
 2016, these browsers include:
 
 * Chrome 31+
@@ -21,7 +21,7 @@ API](https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html#tts-sectio
 
 <div class="infusion-docs-note">
     <strong>Note:</strong> find the latest browser support data for Web Speech Synthesis API from <a
-    href="https://caniuse.com/web-speech">caniuse.com</a>.
+    href="https://caniuse.com/speech-recognition">caniuse.com</a>.
 </div>
 
 ## Creator
@@ -376,7 +376,7 @@ speech:
 
 Configuration of the Text To Speech component can be done through `model.utteranceOpts`. This model path is a Javascript
 object that contains attributes that users can use to define the behaviour of the [SpeechSynthesisUtterance
-instance](https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html#utterance-attributes) (a part of the web
+instance](https://wicg.github.io/speech-api/#utterance-attributes) (a part of the web
 speech API that the Text To Speech component interacts with).
 
 <div class="infusion-docs-note">
@@ -465,16 +465,16 @@ fluid.textToSpeech({
             <th>Description</th>
             <td>
                 The <code>voice</code> attribute must be a <a
-                href="https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html#speechsynthesisvoice"><code>SpeechSynthesisVoice</code></a>
+                href="https://wicg.github.io/speech-api/#speechsynthesisvoice"><code>SpeechSynthesisVoice</code></a>
                 object that specifies the speech synthesis voice that the web application wishes to use. Calling the <a
                 href="#getvoices">getVoices</a> method returns an array of all available voices, from which you can
                 select a valid <code>SpeechSynthesisVoice</code>, or you can call the <code><a
-                href="https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html#dfn-ttsgetvoices">SpeechSynthesis.getVoices()</a></code>
+                href="https://wicg.github.io/speech-api/#dom-speechsynthesis-getvoices">SpeechSynthesis.getVoices()</a></code>
                 function of the browser directly.
                 <div class="infusion-docs-note">
                     <strong>Note:</strong> in some browsers (such as Chrome), the voice list is populated after the page
                     is loaded, and you may need to wait for the <a
-                    href="https://dvcs.w3.org/hg/speech-api/raw-file/tip/webspeechapi.html#dfn-ttsonvoiceschanged">voiceschanged</a>
+                    href="https://wicg.github.io/speech-api/#dom-speechsynthesis-onvoiceschanged">voiceschanged</a>
                     event to get a full list.
                 </div>
             </td>

src/documents/tutorial-developerIntroduction/DeveloperIntroductionToInfusionFramework-OpeningRemarks.md

@@ -13,7 +13,7 @@ time.
 The introduction assumes:
 
 * You are familiar with the basics of [JavaScript](https://developer.mozilla.org/en-US/docs/Learn/JavaScript).
-* You know how to use a browser's [developer tools](https://developer.mozilla.org/en-US/docs/Learn/Common_questions/What_are_browser_developer_tools)
+* You know how to use a browser's [developer tools](https://developer.mozilla.org/en-US/docs/Learn/Common_questions/Tools_and_setup/What_are_browser_developer_tools)
   to access a console.
 * Ideally, you should also have some experience with the [jQuery](https://jquery.com/) JavaScript library that Infusion
   is built atop.

src/documents/tutorial-prefsFrameworkMinimalFootprint/MinimalFootprint.md

@@ -11,11 +11,11 @@ optimizations.
 
 Below are some resources which discuss general website optimization strategies:
 
-* [https://developers.google.com/speed/](https://developers.google.com/speed/)
-* [https://developers.google.com/speed/docs/insights/rules](https://developers.google.com/speed/docs/insights/rules)
-* [https://developers.google.com/web/fundamentals/performance](https://developers.google.com/web/fundamentals/performance)
-* [https://www.smashingmagazine.com/2014/09/improving-smashing-magazine-performance-case-study/](https://www.smashingmagazine.com/2014/09/improving-smashing-magazine-performance-case-study/)
-* [https://hpbn.co](https://hpbn.co)
+* [Analyze and optimize your website with PageSpeed tools](https://developers.google.com/speed/)
+* [Get Started with the PageSpeed Insights API](https://developers.google.com/speed/docs/insights/v5/get-started)
+* [Why does speed matter?](https://web.dev/learn/performance/why-speed-matters)
+* [Improving Smashing Magazine’s Web Performance: A Case Study](https://www.smashingmagazine.com/2014/09/improving-smashing-magazine-performance-case-study/)
+* [High Performance Browser Networking](https://hpbn.co)
 
 ## Optimization of the Preferences Framework