chore: final intro edits

website/docs/guides/accessibility/00-index.mdx

@@ -48,14 +48,14 @@ We advise against this since using a [Link](/docs/components/link) is the best w
 :::
 
 Of course, a significant portion of an accessible user experience happens _external_ to the design system's components and foundations, where we cannot provide guarantees.
-For those, we do our best to provide guardrails and help our users safely break the rules.
+For those, we do our best to provide guardrails, guidelines, and help our users safely break the rules.
 
 ### Make the right thing the easy thing
 
 We believe that application and content authors know best how their application should behave and how their content should be composed.
 This includes behavior for people using assistive technology like screen readers or voice control software.
 
-But accessibility can be hard and it's easy to make mistakes or oversights, so to address this, we provide guardrails and reasonable defaults to help **make the right thing the easy thing**.
+But accessibility can be hard and it's easy to make mistakes or oversights, so to address this tension, we provide guardrails and reasonable defaults to help **make the right thing the easy thing**.
 
 This also means that application and content authors can use the design system in ways that aren't accessible, either accidentally or due to a misunderstanding about accessible design and development.
 Since we know that our application and content authors want to make accessible products, we've created these accessibility guides to help cover the areas of accessibility that our components, foundations, and patterns don't or can't cover.