Skip to content

Commit 16bb839

Browse files
Update 16/umbraco-cms/customizing/extending-overview/extension-registry/extension-manifest.md
Co-authored-by: Richard Jackson <[email protected]>
1 parent 8fd0c0f commit 16bb839

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

16/umbraco-cms/customizing/extending-overview/extension-registry/extension-manifest.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ These fields are all required and have the following meaning:
3636
### Additional Manifest properties
3737
Most extension types support the use of the following generic features for their Manifest:
3838

39-
* `weight` - Define a weight to determine the importance or visual order of this extension. A higher weight gives a more prominent position. For instance, for a dashboard it determines it's order between other dashboards.
39+
* `weight` - Define a weight to determine the importance or visual order of this extension. A higher weight gives a more prominent position. For instance, for a dashboard it determines its order between other dashboards.
4040
* `overwrites` - If replacing an existing extension, this define one or more Extension Aliases that this extension should replace. Read more in [Replace, Exclude or Unregister extensions](replace-exclude-or-unregister.md).
4141
* `conditions` - Define one or more conditions that must pass for the extension to become available. For instance, don't show a section if you don't have the proper rights. Read more in [Extension Conditions](../extension-conditions.md).
4242
* `kind` - Some extension types can reference a predefined Kind. By specifying a Kind, the manifest inherits the Kind's properties. This allows for reuse of predefined settings. See [Extension Kind](../extension-kind.md).

0 commit comments

Comments
 (0)