Update links to term examples (#2377)

Author: daniel-montalvo

pages/glossary/accessible-name.md

@@ -29,4 +29,4 @@ For more details, see [examples of accessible name][].
 - The [accessible name and description computation][] suggest that if an `aria-labelledby` attribute refers to an existing but empty element, the computation should stop and return an empty name without defaulting to the next steps. Several user agents and assistive technologies chose to use the next step in the computation in this case.
 
 [accessible name and description computation]: https://www.w3.org/TR/accname 'Accessible Name and Description Computation'
-[examples of accessible name]: https://act-rules.github.io/pages/examples/accessible-name/
+[examples of accessible name]: https://www.w3.org/WAI/standards-guidelines/act/rules/terms/accessible-name/examples/

pages/glossary/default-page-language.md

@@ -17,4 +17,4 @@ For more details, see [examples of default language][].
 [document]: https://dom.spec.whatwg.org/#document-element 'DOM document element, as of 2020/06/05'
 [most common language]: #most-common-element-language 'Definition of Most Common Language of an Element'
 [web page]: #web-page-html 'Definition of Web Page (HTML)'
-[examples of default language]: https://act-rules.github.io/pages/examples/element-language/
+[examples of default language]: https://www.w3.org/WAI/standards-guidelines/act/rules/terms/element-language/examples/

pages/glossary/included-in-the-accessibility-tree.md

@@ -15,4 +15,4 @@ For more details, see [examples of included in the accessibility tree][].
 
 [Programmatically hidden](#programmatically-hidden) elements are removed from the accessibility tree. However, some browsers will leave [focusable](#focusable) elements with an `aria-hidden` attribute set to `true` in the accessibility tree. Because they are hidden, these elements are considered **not** included in the accessibility tree. This may cause confusion for users of assistive technologies because they may still be able to interact with these focusable elements using sequential keyboard navigation, even though the element should not be included in the accessibility tree.
 
-[examples of included in the accessibility tree]: https://act-rules.github.io/pages/examples/included-in-the-accessibility-tree/
+[examples of included in the accessibility tree]: https://www.w3.org/WAI/standards-guidelines/act/rules/terms/included-in-the-accesibility-tree/examples/

pages/glossary/most-common-language.md

@@ -16,4 +16,4 @@ For more details, see [examples of most common language][].
 
 [language subtag registry]: http://www.iana.org/assignments/language-subtag-registry/language-subtag-registry 'Language Subtag Registry'
 [text inheriting its programmatic language]: #text-inheriting-language 'Definition of Text Inheriting its Programmatic Language from an Element'
-[examples of most common language]: https://act-rules.github.io/pages/examples/element-language/
+[examples of most common language]: https://www.w3.org/WAI/standards-guidelines/act/rules/terms/element-language/examples/

pages/glossary/programmatic-label.md

@@ -17,4 +17,4 @@ For more details, see [examples of programmatic label][].
 **Note**: a given element may have more than one programmatic label.
 
 [labeled control]: https://html.spec.whatwg.org/multipage/forms.html#labeled-control 'Definition of labeled control'
-[examples of programmatic label]: https://act-rules.github.io/pages/examples/programmatic-label/
+[examples of programmatic label]: https://www.w3.org/WAI/standards-guidelines/act/rules/terms/programmatic-label/examples/

pages/glossary/visible.md

@@ -14,4 +14,4 @@ Content is considered _visible_ if making it fully transparent would result in a
 
 [Content is defined in WCAG](https://www.w3.org/TR/WCAG22/#dfn-content).
 
-For more details, see [examples of visible](https://act-rules.github.io/pages/examples/visible/).
+For more details, see [examples of visible](https://www.w3.org/WAI/standards-guidelines/act/rules/terms/visible/examples/).