diff --git a/storybook/stories/contributing/contributing-components.txt b/storybook/stories/contributing/contributing-components.txt
index 95d0b420f65fd..d67b2ed19cd44 100644
--- a/storybook/stories/contributing/contributing-components.txt
+++ b/storybook/stories/contributing/contributing-components.txt
@@ -170,7 +170,7 @@ In these situations, one possible approach is to "soft-deprecate" a given legacy
 2. Updating all places in Gutenberg that use that API.  
 3. Adding deprecation warnings (only after the previous point is completed).
 
-When adding new components or new props to existing components, consider creating a private or experimental version until the changes are stable enough to be exposed publicly.
+When adding new components or new props to existing components, consider creating a private or experimental version until the changes are stable enough to expose publicly.
 
 Learn more:  
 - [How to preserve backward compatibility for a React Component](https://developer.wordpress.org/block-editor/contributors/code/backward-compatibility/#how-to-preserve-backward-compatibility-for-a-react-component)