Apply suggestions from code review

jpmorganchase · Nov 11, 2024 · 251dddb · 251dddb
1 parent 7609c65
commit 251dddb
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/site/docs/about/glossary.mdx b/site/docs/about/glossary.mdx
@@ -39,8 +39,8 @@ For an overview of theming, refer to our [theming documentation](/salt/themes/in
 
 ## Disabled state
 
-A component in a disabled state is completely non-interactive as it isn't considered relevant to the user’s workflow at that time. As the function isn't available to the user, the component doesn't need to meet minimum contrast requirements and is often displayed as visually muted. Consider if a disabled state is the right UI pattern, or if a progressive reveal might be more appropriate. Salt doesn't offer validation states (error, warning, or success) for disabled components, as these imply required user action.
+A component in a disabled state is completely non-interactive as it isn’t considered relevant to the user’s workflow at that time. As the function isn’t available to the user, the component doesn’t need to meet minimum contrast requirements and is often displayed as visually muted. Consider if a disabled state is the correct UI pattern or if a progressive reveal might be more appropriate. Salt doesn’t offer validation states (error, warning, or success) for disabled components, as these imply required user action.
 
 ## Read-only state
 
-A component in a read-only state is considered relevant to the user’s workflow, allowing users to view and interact with the content without modifying it. It must meet accessibility requirements, including minimum contrast. The system supports validation states (error, warning or success) for read-only components. While disabled states are usually not detected by screen readers, read-only elements are accessible by screen reader.
+A component in a read-only state is considered relevant to the user’s workflow, allowing users to view and interact with the content without modifying it. It must meet accessibility requirements, including minimum contrast. The system supports validation states (error, warning or success) for read-only components. While disabled states are usually not detected by screen readers, read-only elements are accessible by screen readers.