Merge branch 'feature/7360_extension_registry' of https://github.com/Luuk1983/UmbracoDocs into feature/7360_extension_registry

Author: Luuk Peters

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

@@ -1,6 +1,6 @@
 ---
 description: >-
-  Bringing new UI or additional features to the Backoffice is done by
+  You can bring new UI or additional features to the Backoffice by
   registering an Extension via an Extension Manifest.
 ---
 
@@ -54,7 +54,7 @@ There are two additional, optional properties that can be useful:
 * `version` - the version of the package that is displayed in the backoffice in the overview of installed packages. This is also used for package migrations.
 
 
-This is an example of a full umbraco-package.json that registers two localization extensions:
+This is an example of a full `umbraco-package.json` that registers two localization extensions:
 
 ```json
 {
@@ -74,7 +74,7 @@ This is an example of a full umbraco-package.json that registers two localizatio
     },
     {
       "type": "localization",
-      "alias": "MyCustomizations.Localize.NlNl",
+      "alias": "MyCustomizations.Localize.DkDk",
       "name": "Danish",
       "meta": {
         "culture": "dk"
@@ -88,7 +88,7 @@ This is an example of a full umbraco-package.json that registers two localizatio
 
 ## Advanced Registration
 ### The Bundle Approach
-Instead of registering each manifest in the `umbraco-package.json`, you can have multiple manifests and build them into a bundle. You then register this bundle in a single `bundle` extension. In larger projects with a lot of extensions, this allows you to keep your umbraco-package.json file leaner. Read more in the [bundle approach](../extension-types/bundle.md).
+Instead of registering each manifest in the `umbraco-package.json`, you can have multiple manifests and build them into a bundle. You then register this bundle in a single `bundle` extension. In larger projects with a lot of extensions, this allows you to keep your `umbraco-package.json` file cleaner. Read more in the [bundle approach](../extension-types/bundle.md).
 
 ### The Entry Point Approach
 The Entry Point is an extension that executes a method on startup. You can use this for different tasks, such as performing initial configuration and registering other Extension Manifests. Read more in [the entry point approach](../extension-types/backoffice-entry-point.md).

16/umbraco-cms/customizing/extending-overview/extension-registry/replace-exclude-or-unregister.md

@@ -10,13 +10,13 @@ Besides adding extensions to Umbraco, sometimes you want to change what is alrea
 
 
 ## Replace
-You can have an extension that replaces another extension.
+You can replace an existing extension by another one.
 You can do this by defining the `overwrites` property in your [Extension Manifest](extension-manifest.md) with one Extension Alias. For multiple `overwrites` you can provide the Extension Aliases that need to be replaced as an array.
 
 
 
 
-This example overrides the save and preview button with an external preview button (single overwrite):
+This example overrides the `save and preview` button with an external "preview" button (single overwrite):
 
 ```typescript
 const manifest = {
@@ -29,7 +29,7 @@ const manifest = {
 ```
 
 
-This example overrides both the save and preview button as well as the save button with an external preview button (multiple overwrite):
+This example overrides both the `save and preview` button as well as the `save` button with an external "preview" button (multiple overwrite):
 
 ```typescript
 const manifest = {
@@ -46,7 +46,7 @@ If your extension has conditions, the overwritten extensions will only be hidden
 
 
 ## Exclude
-When you exclude an extension, the extension will never be displayed. This allows you to permanently hide, for example, a menu or a button. This does not unregister the extensions, but rather flags them as excluded. This also means that no one else can register an extension with the same alias as the excluded extension.
+When you exclude an extension, the extension will never be displayed. This allows you to permanently hide, for example, a menu or a button. This does not unregister the extension, but rather flags it as excluded. This also means that no one else can register an extension with the same alias as the excluded extension.
 
 
 {% hint style="warning" %}
@@ -66,7 +66,7 @@ When and where you execute this code depends on your situation. In many cases, i
 
 
 ## Unregister
-You can also choose to unregister an extension. You should only use this on extensions you registered yourself and have control over. Otherwise, you might try to remove an extension before it is registered. A use case for this is if you temporarily registered an extension and you want to remove it again.
+You can also choose to unregister an extension. You should only use this on extensions you registered yourself and have control over. Otherwise, you might try to remove an extension before it is registered. A use case for this, is if you temporarily registered an extension and you want to remove it again.
 
 In other cases, you can use the `overwrites` or `exclude` option. The difference with the `exclude` approach is that unregistering removes the extension from the Extension Registry. This allows you to re-register extensions with the same alias.