Small content fixes for rari (#36617)

* Fix macros on kitchensink page * content fixes * small content issues for rari/yari parity
mdn · Nov 1, 2024 · 3a004b5 · 3a004b5
1 parent b7a7c44
commit 3a004b5
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 7 deletions.
diff --git a/files/en-us/web/accessibility/aria/aria_live_regions/index.md b/files/en-us/web/accessibility/aria/aria_live_regions/index.md
@@ -142,7 +142,7 @@ Elements with the following [`role="…"`](/en-US/docs/Web/Accessibility/ARIA/Ro
   </tr>
   <tr>
    <td>alert</td>
-   <td>Error or warning message that flashes on the screen. Alerts are particularly important for client side validation notices to users. <a href="https://www.w3.org/WAI/ARIA/apg/example-index/alert/alert.html" class="external" rel=" noopener">Alert Example.</a></td>
+   <td>Error or warning message that flashes on the screen. Alerts are particularly important for client side validation notices to users. <a href="https://www.w3.org/WAI/ARIA/apg/example-index/alert/alert.html" class="external" rel="noopener">Alert Example.</a></td>
    <td>To maximize compatibility, some people recommend adding a redundant <code>aria-live="assertive"</code> when using this role. However, adding both <code>aria-live</code> and <code>role="alert"</code> causes double speaking issues in VoiceOver on iOS.</td>
   </tr>
   <tr>

diff --git a/files/en-us/web/accessibility/aria/roles/dialog_role/index.md b/files/en-us/web/accessibility/aria/roles/dialog_role/index.md
@@ -137,8 +137,6 @@ When the dialog is correctly labeled and focus is moved to an element (often an
 
 {{Specifications}}
 
-Coming soon
-
 ## See also
 
 - [ARIA: alertdialog role](/en-US/docs/Web/Accessibility/ARIA/Roles/alertdialog_role)

diff --git a/files/en-us/web/accessibility/understanding_wcag/perceivable/index.md b/files/en-us/web/accessibility/understanding_wcag/perceivable/index.md
@@ -288,7 +288,7 @@ This guideline refers to the ability of content to be consumed by users in multi
             button that can be activated by keyboard or other means.
           </li>
         </ul>
-        <div class="note">
+        <div class="note notecard">
           <p>
             <strong>Note:</strong> Conveying instructions solely by color is
             related, but covered in a different guideline — 1.4.1.

diff --git a/files/en-us/web/accessibility/understanding_wcag/understandable/index.md b/files/en-us/web/accessibility/understanding_wcag/understandable/index.md
@@ -330,7 +330,7 @@ This guideline centers around helping users enter correct information when requi
           help the user correct their inputs. For screen reader users, you can
           use aria live regions to alert the user to a change on the page.
         </p>
-        <div class="note">
+        <div class="note notecard">
           <p>
             <strong>Note:</strong> Server-side validation should <em>always</em> be
             used alongside client-side validation. Client-side validation is too

diff --git a/files/en-us/web/security/practical_implementation_guides/tls/index.md b/files/en-us/web/security/practical_implementation_guides/tls/index.md
@@ -68,8 +68,8 @@ APIs or websites not intended for public access should entirely disable the use
 
 To fix the "different hosts" problem:
 
-1. First, redirect from http://example.com/ to https://example.com/.
-2. Next, redirect from https://example.com/ to https://example.org/.
+1. First, redirect from http\://example.com/ to https\://example.com/.
+2. Next, redirect from https\://example.com/ to https\://example.org/.
 
 ### Examples