Fixes remaining issues in [overall] module numbering w3c#385

content/designer/images-and-graphics.md

@@ -205,7 +205,7 @@ Students should be able to:
 
 Optional ideas to teach the learning outcomes:
 
-* Provide examples of complex images and graphics, such as charts, diagrams, maps, and infographics. Refer back to [Module 1: Visual Design, Topic: Color](/curricula/designer-modules/visual-design/#topic-use-of-color). Explain that they need to have a color contrast ratio of at least 3:1, as they are necessary to understand the content. For references on how to provide complex graphics that meet the required color contrast ratio, see technique [G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text](https://www.w3.org/WAI/WCAG21/Techniques/general/G18.html).
+* Provide examples of complex images and graphics, such as charts, diagrams, maps, and infographics. Refer back to [Designer Module 1: Visual Design, Topic: Color](/curricula/designer-modules/visual-design/#topic-use-of-color). Explain that they need to have a color contrast ratio of at least 3:1, as they are necessary to understand the content. For references on how to provide complex graphics that meet the required color contrast ratio, see technique [G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text](https://www.w3.org/WAI/WCAG21/Techniques/general/G18.html).
 * Explain that complex images also need to have text descriptions that allow people to understand and interact with such images without having to look at them. Explain that providing these text alternatives is a designers' responsibility, whereas providing the text descriptions is a responsibility shared with the content author.
 
 #### Ideas to Assess Knowledge for Topic

content/developer/custom-widgets.md

@@ -93,7 +93,7 @@ Topics to achieve the learning outcomes:
 
 {% include excol.html type="middle" %}
 
-Build on previous modules, in particular [Module 5: Forms](/curricula/developer-modules/forms/) and [Module 1: Page Structure](/curricula/developer-modules/page-structure/) to explain the importance of proper role definitions for widgets. Demonstrate how native HTML interactive elements, such as controls and links, provide such semantics by default. Demonstrate and explain the use of WAI-ARIA attributes to define additional roles when HTML interactive elements are not sufficient.
+Build on previous modules, in particular [Developer Module 5: Forms](/curricula/developer-modules/forms/) and [Developer Module 1: Page Structure](/curricula/developer-modules/page-structure/) to explain the importance of proper role definitions for widgets. Demonstrate how native HTML interactive elements, such as controls and links, provide such semantics by default. Demonstrate and explain the use of WAI-ARIA attributes to define additional roles when HTML interactive elements are not sufficient.
 
 #### Learning Outcomes for Topic
 
@@ -133,7 +133,7 @@ Optional ideas to support assessment:
 
 {% include excol.html type="middle" %}
 
-Refer back to [Module 5: Forms](/curricula/developer-modules/forms/) to review the importance of labels for controls. Demonstrate how custom widgets also require similar labeling techniques, and explain how to provide accessible names for widgets. Demonstrate how some custom widgets require additional descriptions, and explain how to provide such descriptions for widgets.
+Refer back to [Developer Module 5: Forms](/curricula/developer-modules/forms/) to review the importance of labels for controls. Demonstrate how custom widgets also require similar labeling techniques, and explain how to provide accessible names for widgets. Demonstrate how some custom widgets require additional descriptions, and explain how to provide such descriptions for widgets.
 
 #### Learning Outcomes for Topic
 

content/developer/forms.md

@@ -55,7 +55,7 @@ Skills required for this module:
 {% include excol.html type="middle" %}
 
 * [Foundation Prerequisites](/curricula/developer-modules/#foundation-prerequisites)
-* [Developer Modules](/curricula/curriculum-for-developers)
+* [Developer Modules](/curricula/developer-modules)
   * [Module 1: Page Structure](/curricula/developer-modules/page-structure/)
 * Basic knowledge of [HTML forms {% include_cached icon.html name="external-link" %}](https://html.spec.whatwg.org/multipage/forms.html#forms)
 
@@ -91,7 +91,7 @@ Skills required for this module:
   * [HTML date, time, and input formats {% include_cached icon.html name="external-link" %}](https://html.spec.whatwg.org/multipage/forms.html#input-author-notes)
 * In-depth knowledge of:
   * [Foundation Prerequisites](/curricula/developer-modules/#foundation-prerequisites)
-  * [Page Structure](/curricula/developer-modules/page-structure/)
+  * [Developer Module 1: Page Structure](/curricula/developer-modules/page-structure/)
 
 {% include excol.html type="end" %}
 
@@ -105,7 +105,7 @@ Topics to achieve the learning outcomes:
 
 {% include excol.html type="middle" %}
 
-Explain the use of HTML elements and, if necessary, WAI-ARIA attributes to provide form controls and labels for form controls. Demonstrate how these semantics benefit different users in different situations, such as people using screen readers, screen magnification, voice interaction, and other assistive technologies. Non-standard form controls are addressed in [Module 6: Custom Widgets](/curricula/developer-modules/custom-widgets/).
+Explain the use of HTML elements and, if necessary, WAI-ARIA attributes to provide form controls and labels for form controls. Demonstrate how these semantics benefit different users in different situations, such as people using screen readers, screen magnification, voice interaction, and other assistive technologies. Non-standard form controls are addressed in [Developer Module 6: Custom Widgets](/curricula/developer-modules/custom-widgets/).
 
 #### Learning Outcomes for Topic
 

content/developer/menus.md

@@ -59,7 +59,7 @@ Skills required for this module:
 {% include excol.html type="middle" %}
 
 * [Foundation Prerequisites](/curricula/developer-modules/#foundation-prerequisites)
-* [Module 1: Page Structure](/curricula/developer-modules/page-structure/) from [Developer Modules](/curricula/developer-modules/)
+* [Developer Module 1: Page Structure](/curricula/developer-modules/page-structure/)
 
 {% include excol.html type="end" %}
 
@@ -82,7 +82,7 @@ Skills required for this module:
   * [WAI-ARIA landmark roles](https://www.w3.org/TR/wai-aria/#landmark_roles)
 * In-depth knowledge of:
   * [Foundation Prerequisites](/curricula/developer-modules/#foundation-prerequisites)
-  * [Module 1: Page Structure](/curricula/developer-modules/page-structure/) from [Developer Modules](/curricula/developer-modules/)
+  * [Developer Module 1: Page Structure](/curricula/developer-modules/page-structure/)
 
 {% include excol.html type="end" %}
 
@@ -96,7 +96,7 @@ Topics to achieve the learning outcomes:
 
 {% include excol.html type="middle" %}
 
-Build on [Module 1: Page Structure](/curricula/developer-modules/page-structure/) to explain the use of HTML and WAI-ARIA to convey structure. Relate this to the structure of menus, in particular using lists and list items.
+Build on [Developer Module 1: Page Structure](/curricula/developer-modules/page-structure/) to explain the use of HTML and WAI-ARIA to convey structure. Relate this to the structure of menus, in particular using lists and list items.
 
 #### Learning Outcomes for Topic
 
@@ -206,7 +206,7 @@ Optional ideas to support assessment:
 
 {% include excol.html type="middle" %}
 
-Show examples of specific scenarios where application menus can be used. Application menus are commonly used in rich applications, which are further discussed in [Module 7 Rich Applications](/curricula/developer-modules/rich-applications). Explain the uses of additional WAI-ARIA roles and properties to mark up application menus. Refer to coding techniques to make application menus operable using various input devices, including keyboard only.
+Show examples of specific scenarios where application menus can be used. Application menus are commonly used in rich applications, which are further discussed in [Developer Module 7 Rich Applications](/curricula/developer-modules/rich-applications). Explain the uses of additional WAI-ARIA roles and properties to mark up application menus. Refer to coding techniques to make application menus operable using various input devices, including keyboard only.
 
 #### Learning Outcomes for Topic