diff --git a/src/Umbraco.Web.UI.Client/storybook/stories/extending/workspaces/context.mdx b/src/Umbraco.Web.UI.Client/storybook/stories/extending/workspaces/context.mdx
index cb9e6a0b86..b2da374899 100644
--- a/src/Umbraco.Web.UI.Client/storybook/stories/extending/workspaces/context.mdx
+++ b/src/Umbraco.Web.UI.Client/storybook/stories/extending/workspaces/context.mdx
@@ -13,9 +13,9 @@ TODO: Extend the description of a workspace
 (rough notes)
 
 - A workspace context knows about its entity type (e.g. content, media, member, etc.) and holds its unique string (e.g.: key).
-- Most workspaces contexts hold a draft state of its entity data. It is a copy of the entity data that can be modified at runtime and sent to the server to be saved.
+- Most workspace contexts hold a draft state of its entity data. It is a copy of the entity data that can be modified at runtime and sent to the server to be saved.
 
-If a workspace wants to utilize Property Editor UIs, then it must provide a variant context for the property editors. The variant-context is the generic interface between workspace and property editors. See variant contexts for more info.
+If a workspace wants to utilize Property Editor UIs, then it must provide a variant context for the property editors. The property-dataset context is the generic interface between workspace and property editors. See variant contexts for more info.
 
 TODO: More points and examples: