correct links and text

Author: nielslyngsoe

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

@@ -1,26 +1,38 @@
-# Extension Manifest
+---
+description:
+---
 
-{% hint style="warning" %}
-This page is a work in progress and may undergo further revisions, updates, or amendments. The information contained herein is subject to change without notice.
-{% endhint %}
+# Extension Manifest
 
 Each Extension Manifest has to declare its type, this is used to determine where it hooks into the system. It also looks at what data is required to declare within it.
 
 The abilities of the extensions rely on the specific extension type. The Type sets the scene for what the extension can do and what it needs to be utilized. Some extension types rely on a reference to other extensions.
 
-The pages of this article describe all the extension types that Backoffice supports. Here is a list of the most common types:
+The following overview lists all the available extension types:
 
-{% content-ref url="../../../tutorials/creating-a-custom-dashboard/" %}
-[creating-a-custom-dashboard](../../../tutorials/creating-a-custom-dashboard/)
+{% content-ref url="../extension-types/" %}
+[extension-types](../extension-types/)
 {% endcontent-ref %}
 
-{% content-ref url="../../property-editors/composition/" %}
-[composition](../../property-editors/composition/)
-{% endcontent-ref %}
 
-{% content-ref url="../../section-trees/" %}
-[section-trees](../../section-trees/)
-{% endcontent-ref %}
+## Extension Manifest Format
+
+A Extension Manifest can be written either as JavaScript Object or a JSON Object.
+
+There is a few general properties, the required set of properties consists of the `type`, `alias` and `name`.
+
+```typescript
+const manifest = {
+    type: '...',
+    alias: 'my.customization',
+    name: 'My customization'
+    ...
+};
+```
+
+The `type` defined what it is declaring
+The `alias` is a unique identifier for this manifest. It must be globally unique, so make sure to prefix with something that makes your extension unique.
+The `name` is a representational name of this manifest, this does not need to be unique but such can be beneficial when debugging extensions.
 
 ## Declare Extension Manifest
 
@@ -47,7 +59,7 @@ The bundle extension type can be used for declaring multiple Extension Manifests
 
 The bundle declares a single JavaScript file that will be loaded at startup. All the Extension Manifests exported from this Module will be registered in the Extension Registry.
 
-Read more about the `bundle` extension type in the [Bundle](../../../extending/extending-overview/extension-registry/bundle.md) article.
+Read more about the `bundle` extension type in the [Bundle](../extension-types/bundle.md) article.
 
 ### Using `backofficeEntryPoint` as your foundation
 
@@ -57,4 +69,4 @@ The entry point declares a single JavaScript file that will be loaded and run wh
 
 The `entryPbackofficeEntryPointoint` extension is also the way to go if you want to load in external libraries such as jQuery, Angular, React, etc. You can use the `backofficeEntryPoint` to load in the external libraries to be shared by all your extensions. Loading **global CSS files** can also be used in the `backofficeEntryPoint` extension.
 
-Read more about the `backofficeEntryPoint` extension type in the [Entry Point](../../../extending/extending-overview/extension-registry/entry-point.md) article.
+Read more about the `backofficeEntryPoint` extension type in the [Entry Point](../extension-types/entry-point.md) article.

15/umbraco-cms/customizing/package-manifest.md

@@ -1,10 +1,10 @@
 ---
-description: An extension begins with a Package Manifest
+description: An extension begins with a Umbraco Package Manifest
 ---
 
-# Package Manifest
+# Umbraco Package Manifest
 
-A Package is declared via an Umbraco Package Manifest. This describes the Package and declares one or more UI Extensions. The Package Manifest is a JSON file that is stored in the `App_Plugins/{YourPackageName}` folder. The file is named `umbraco-package.json`.
+A Package is declared via an Umbraco Package Manifest. This describes the Package and declares one or more UI Extensions. The Manifest is a JSON file that is stored in the `App_Plugins/{YourPackageName}` folder. The file is named `umbraco-package.json`.
 
 ## Sample Manifest
 
@@ -120,13 +120,9 @@ Umbraco supports the current specification of the property as outlined on MDN We
 
 ### Extensions
 
-The `extensions` field is an array of UI Extension objects. Each object describes a single UI Extension.
+The `extensions` field is an array of Extension Manifest objects. Each object describes a single client extension.
 
-There are three generic fields that are common to all UI Extensions:
-
-* `type` - The type of the UI Extension.
-* `alias` - The alias of the UI Extension. This must be unique.
-* `name` - The name of the UI Extension.
+Read more about these in the [Extension Manifests article](./extending-overview/extension-registry/extension-manifest.md).
 
 These are the current types of UI Extensions: