diff --git a/files/en-us/learn/html/introduction_to_html/document_and_website_structure/index.html b/files/en-us/learn/html/introduction_to_html/document_and_website_structure/index.html
index 83271908e0c8f16..2474d17b01459c4 100644
--- a/files/en-us/learn/html/introduction_to_html/document_and_website_structure/index.html
+++ b/files/en-us/learn/html/introduction_to_html/document_and_website_structure/index.html
@@ -178,7 +178,7 @@ <h2 id="HTML_layout_elements_in_more_detail">HTML layout elements in more detail
  <li>{{HTMLElement('footer')}} represents a group of end content for a page.</li>
 </ul>
 
-<p>Each of the aformentioned elements can be clicked on to read the corresponding article in the "HTML element reference" section, providing more detail about each one.</p>
+<p>Each of the aforementioned elements can be clicked on to read the corresponding article in the "HTML element reference" section, providing more detail about each one.</p>
 
 <h3 id="Non-semantic_wrappers">Non-semantic wrappers</h3>
 
diff --git a/files/en-us/web/accessibility/aria/roles/dialog_role/index.html b/files/en-us/web/accessibility/aria/roles/dialog_role/index.html
index 3d350e32a95d1f1..9dddedecb273d2f 100644
--- a/files/en-us/web/accessibility/aria/roles/dialog_role/index.html
+++ b/files/en-us/web/accessibility/aria/roles/dialog_role/index.html
@@ -54,7 +54,7 @@ <h4 id="Focus_management">Focus management </h4>
  <li>After the dialog is dismissed, keyboard focus should be moved back to where it was before it moved into the dialog. Otherwise the focus can be dropped to the beginning of the page.</li>
  <li>For most dialogs, the expected behavior is that the dialog's tab order <em>wraps</em>, which means that when the user tabs through the focusable elements in the dialog, the first focusable element will be focused after the last one has been reached. In other words, the tab order should be contained within and by the dialog.</li>
  <li>If the dialog can be moved or resized, ensure that these actions must be performable by keyboard users as well as mouse users. Similarly, if a dialog provides special features like toolbars or context menus, these must be reachable and operable by keyboard users as well.</li>
- <li>Dialogs can be modal or non-modal. When a <em>modal</em> dialog appears on the screen, it's not possible to interact with any page content outside the dialog. In other words, the main application UI or page content is considered to be temporarily disabled as long as the modal dialog is showing. For <em>non-modal</em> dialogs it is still possible to interact with content outside of the dialog while the dialog is showing. Note that for non-modal dialogs there will have to be a global keyboard shortcut that allows focus to be moved between opened dialogs and the main page. For more information see the <a href="/en-US/docs/ARIA/ARIA_Guides/Managing_Modal_and_Non_Modal_Dialogs">Managing Modal and Non Modal Dialogs</a> guide.</li>
+ <li>Dialogs can be modal or non-modal. When a <em>modal</em> dialog appears on the screen, it's not possible to interact with any page content outside the dialog. In other words, the main application UI or page content is considered to be temporarily disabled as long as the modal dialog is showing. For <em>non-modal</em> dialogs it is still possible to interact with content outside of the dialog while the dialog is showing. Note that for non-modal dialogs there will have to be a global keyboard shortcut that allows focus to be moved between opened dialogs and the main page.</li>
 </ul>
 
 <h3 id="Associated_ARIA_roles_states_and_properties">Associated ARIA roles, states, and properties</h3>