From 517dc7623691b528ecc7a4ea84349e7450ce928f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niels=20Lyngs=C3=B8?= Date: Wed, 23 Aug 2023 14:28:41 +0200 Subject: [PATCH] correct mdx docs --- .../storybook/stories/extending/registration/conditions.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/Umbraco.Web.UI.Client/storybook/stories/extending/registration/conditions.mdx b/src/Umbraco.Web.UI.Client/storybook/stories/extending/registration/conditions.mdx index 9833605deb..24ae95827f 100644 --- a/src/Umbraco.Web.UI.Client/storybook/stories/extending/registration/conditions.mdx +++ b/src/Umbraco.Web.UI.Client/storybook/stories/extending/registration/conditions.mdx @@ -25,7 +25,7 @@ In this following example we define the manifest for a Workspace Action, this ac conditions: [ { alias: 'Umb.Condition.SectionAlias', - matches: 'My.Example.Workspace' + match: 'My.Example.Workspace' } ] } @@ -37,7 +37,7 @@ Each condition is an object with the following properties: - `alias`- The alias of the condition to utilize. - `...` - The rest of the properties of the object are specific to the condition. -In the above example the `Umb.Condition.SectionAlias` condition is used, this condition takes a property `matches` which must be set to the alias of the section to match. +In the above example the `Umb.Condition.SectionAlias` condition is used, this condition takes a property `match` which must be set to the alias of the section to match. ### Core conditions types