diff --git a/docs/content/ActionMenu.mdx b/docs/content/ActionMenu.mdx
index d057b2b9ef4..10d697cc845 100644
--- a/docs/content/ActionMenu.mdx
+++ b/docs/content/ActionMenu.mdx
@@ -72,7 +72,7 @@ import {ActionMenu} from '@primer/react'
 
 ### With a custom anchor
 
-You can choose to have a different _anchor_ for the Menu dependending on the application's context.
+You can choose to have a different _anchor_ for the Menu depending on the application's context.
 
  
 
diff --git a/docs/content/Autocomplete.mdx b/docs/content/Autocomplete.mdx
index ff8a08dfa84..6ab78ba949d 100644
--- a/docs/content/Autocomplete.mdx
+++ b/docs/content/Autocomplete.mdx
@@ -314,7 +314,7 @@ render(<CustomSortAfterMenuClose />)
 
 #### Custom filtering
 
-In this example, we show any items who's `text` **contains** the input value. By default, we only show items that start with the input value.
+In this example, we show any items whose `text` **contains** the input value. By default, we only show items that start with the input value.
 
 ```javascript live noinline
 const CustomSearchFilter = () => {
diff --git a/docs/content/FormControl.mdx b/docs/content/FormControl.mdx
index 05c36676ee2..ad6c69da4a2 100644
--- a/docs/content/FormControl.mdx
+++ b/docs/content/FormControl.mdx
@@ -350,7 +350,7 @@ render(ValidationExample)
 
 ### FormControl
 
-The container that handles the layout and passes the relevant IDs and ARIA attributes it's children.
+The container that handles the layout and passes the relevant IDs and ARIA attributes its children.
 
 <PropsTable>
   <PropsTableRow
diff --git a/docs/content/drafts/Dialog.mdx b/docs/content/drafts/Dialog.mdx
index c27726b4ec8..f805bf505e3 100644
--- a/docs/content/drafts/Dialog.mdx
+++ b/docs/content/drafts/Dialog.mdx
@@ -10,7 +10,7 @@ import {Dialog} from '@primer/react/drafts'
 
 import State from '../../components/State'
 
-The dialog component the Primer implementation of the ARIA design pattern [Dialog](https://www.w3.org/TR/wai-aria-practices-1.1/#dialog_modal). A dialog is a type of overlay that can be used for confirming actions, asking for disambiguation, and presenting small forms. They generally allow the user to focus on a quick task without having to navigate to a different page.
+The dialog component is the Primer implementation of the ARIA design pattern [Dialog](https://www.w3.org/TR/wai-aria-practices-1.1/#dialog_modal). A dialog is a type of overlay that can be used for confirming actions, asking for disambiguation, and presenting small forms. They generally allow the user to focus on a quick task without having to navigate to a different page.
 
 **Dialogs appear in the page after a direct user interaction**. Don't show dialogs on page load or as system alerts.