Update best-practices.mdx (#7916)

fixes getsentry/sentry#56683

src/docs/product/alerts/best-practices.mdx

@@ -43,7 +43,7 @@ One way to keep alerts from becoming too noisy is to use filters, or “if” co
 - **Prioritize new issues**: If you're frequently getting alerted about old issues, filter your alerts to issues created in the last few days using the `The issue is older or newer than...` filter.
 - **Filter transient issues**: Many issues exhibit a short burst of events that can trip your frequency-based alerts. To filter out these issues, use the `Issue has happened at least {X} times` filter.
 - **Prioritize the latest release**: Use the `The event is from the latest release` filter to make your issue alert only apply to the latest release.
-- **Ignore noisy issues**: If you're seeing alerts from the same issue repeatedly, [ignore the issue](/product/issues/states-triage/#ignore). (This is not an alert configuration setting.)
+- **Archive noisy issues**: If you're seeing alerts from the same issue repeatedly, [archive the issue](/product/issues/states-triage/#archive). (This is not an alert configuration setting.)
 
 ### Routing