diff --git a/understanding/21/status-messages.html b/understanding/21/status-messages.html
index f202bbd64e..694bc5beb9 100644
--- a/understanding/21/status-messages.html
+++ b/understanding/21/status-messages.html
@@ -53,7 +53,7 @@ <h3>Status Message Examples</h3>
 					<li>An application displays a progressbar to indicate the status of an upgrade. The element is assigned a suitable role. The screen reader provides intermittent announcements of the progress. </li>
 					<li>After a user submits a form, text is added to the existing form which reads, "Your form was successfully submitted." The screen reader announces the same message.</li> 
 					<li>After a user unsuccessfully fills in a form because some of the data is in the incorrect format, text is added to the existing form which reads "5 errors on page". The screen reader announces the same message.</li>
-					<li>After a user puts a photo in an album in an online photo app, a <a href="https://material.io/design/components/snackbars.html#">snackbar </a> displays the message "Saved in 'Wedding' album", which is also read by a screen reader.</li>
+					<li>After a user puts a photo in an album in an online photo app, a <a href="https://m3.material.io/components/snackbar/overview">snackbar</a> displays the message "Saved in 'Wedding' album", which is also read by a screen reader.</li>
 				</ul>
 			</section>
 			<section class="example">
@@ -82,7 +82,7 @@ <h4>Removal of status text</h4>
 				</section>
 				<section>
 		<h4>Non-textual status content</h4>
-		<p>Changes in content are not restricted to text changes. Where an icon or sound indicates a status message, this information will be surfaced by the screen reader through a combination of two things: 1) existing WCAG requirements governing text alternatives (under SC 1.1.1 Non-Text Content), and 2) the requirement of this current Success Criterion to supply an appropriate role.</p>
+		<p>Changes in content are not restricted to text changes. Where an icon or sound indicates a status message, this information will be surfaced by the screen reader through a combination of two things: 1) existing WCAG requirements governing text alternatives (under <a href="non-text-content" class="sc">SC 1.1.1 Non-Text Content</a>), and 2) the requirement of this current Success Criterion to supply an appropriate role.</p>
 				</section>
 			</section>