Fixing broken links in Forms tutorials

content/forms/instructions.md

@@ -35,7 +35,7 @@ wcag_techniques:
   - ARIA9
 
 metafooter: true
-last_updated: 2019-07-27
+last_updated: 2024-04-10
 editors:
   - Eric Eggert: "https://www.w3.org/People/yatil/"
   - Shadi Abou-Zahra: "https://www.w3.org/People/shadi/"
@@ -200,7 +200,7 @@ Placeholder text provides instructions or an example of the required data format
 
 While placeholder text provides valuable guidance for many users, **placeholder text is not a replacement for labels**. Assistive technologies, such as screen readers, do not treat placeholder text as labels. Moreover, at the time of writing this tutorial, placeholder text is not broadly supported across assistive technologies and not displayed in older web browsers.
 
-Note: Section [Hidden labels](labels.html#hidden) of this tutorial describes how to hide information visually but keep it available to assistive technology. This same approach can be used to avoid visual redundancy of displaying both labels and placeholder text. Be aware that this makes it very hard for users to review the form. To avoid this problem, JavaScript can be used to make labels appear visually (in the associated label element) above or beside the input that has focus.
+Note: The [Note on hiding elements](/tutorials/forms/labels/#note-on-hiding-elements) section of the Labeling Controls tutorial describes how to hide information visually but keep it available to assistive technology. This same approach can be used to avoid visual redundancy of displaying both labels and placeholder text. Be aware that this makes it very hard for users to review the form. To avoid this problem, JavaScript can be used to make labels appear visually (in the associated label element) above or beside the input that has focus.
 
 {::nomarkdown}
 {% include box.html type="start" title="Example" class="example" %}

content/forms/labels.md

@@ -38,7 +38,7 @@ wcag_techniques:
   - ARIA16
 
 metafooter: true
-last_updated: 2019-07-27
+last_updated: 2024-04-10
 editors:
   - Eric Eggert: "https://www.w3.org/People/yatil/"
   - Shadi Abou-Zahra: "https://www.w3.org/People/shadi/"
@@ -61,7 +61,7 @@ Provide labels to identify all form controls, including text fields, checkboxes,
 
 {% include_cached toc.html %}
 
-Labels need to describe the purpose of the form control. This section of the tutorial describes how to provide labels that are properly associated with form controls. Later sections explain how to provide [instructions](instructions.html), [validate user input](validation.html), and [provide feedback](notifications.html) to help users complete your form.
+Labels need to describe the purpose of the form control. This section of the tutorial describes how to provide labels that are properly associated with form controls. Later sections explain how to provide [instructions](../instructions), [validate user input](../validation), and [provide feedback](../notifications) to help users complete your form.
 
 A label and a form control should be associated with each other either implicitly or explicitly. Web browsers provide the label as a larger clickable area, for example, to select or activate the control. It also ensures that assistive technology can refer to the correct label when presenting a form control.