Skip to content

Commit 3cabb57

Browse files
authored
Fixed typos and grammar
1 parent d0fe36f commit 3cabb57

File tree

1 file changed

+5
-5
lines changed
  • 16/umbraco-cms/customizing/extending-overview/extension-registry

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,19 +4,19 @@ description: >-
44
---
55

66
# Extension Registry
7-
The Umbraco backoffice is built with extensibility in mind. The backoffice without extensions is more or less a blank canvas that is build out using extensions. These extensions dictate how the backoffice functions and looks. All visual elements in an Umbraco installation, like the sections, menus, trees and buttons, are extensions. But extensions also dictate behaviour and the editing experience. So everything in the backoffice is governed (and extendable) by extensions.
7+
The Umbraco backoffice is built with extensibility in mind. The backoffice without extensions is more or less a blank canvas that is built out using extensions. These extensions dictate how the backoffice functions and looks. All visual elements in an Umbraco installation, like the sections, menus, trees, and buttons, are extensions. But extensions also dictate behavior and the editing experience. So everything in the backoffice is governed (and extendable) by extensions.
88

99
{% hint style="info" %}
1010
You can see which extensions are registered in the backoffice by going to Settings > Extensions Insights.
1111
{% endhint %}
1212

13-
All extensions are registered in the extension registry. The registry can be manipulated at any time, meaning you can add or remove extensions at runtime. You as a developer have the same possibilities as an Umbraco HQ developer, which means what HQ can do, you can do. This also means that you can change almost everything that is by default present in Umbraco.
13+
All extensions are registered in the extension registry. The registry can be manipulated at any time, meaning you can add or remove extensions at runtime. You, as a developer, have the same possibilities as an Umbraco HQ developer, which means that what HQ can do, you can do. This also means that you can change almost everything that is by default present in Umbraco.
1414

1515
## [Introduction to Extension Manifest](extension-manifest.md)
16-
An Extension Manifest is a declaration of what you want to register in the Umbraco backoffice. This articles handles the layout and requirements of an Extension Manifest.
16+
An Extension Manifest is a declaration of what you want to register in the Umbraco backoffice. This article handles the layout and requirements of an Extension Manifest.
1717

18-
## [Register an extension](extension-registry.md)
19-
This article handles how to register an extension using an umbraco-package.json file.
18+
## [Register an Extension](extension-registry.md)
19+
This article handles how to register an extension using an `umbraco-package.json` file.
2020

2121
## [Change an existing extension](replace-exclude-or-unregister.md)
2222
Once you understand how to declare your own, you may want to replace or remove existing ones.

0 commit comments

Comments
 (0)