[All Hosts] (manifest) reorg the manifest part of the TOC (#4727)

* [All Hosts] (manifest) reorg the manifest part of the TOC

* format

* format

* typos

* Update docs/includes/manifest-guidance.md

Co-authored-by: Alison McKay <[email protected]>

* Update docs/toc.yml

* add support note

---------

Co-authored-by: Alison McKay <[email protected]>

Author: Rick-Kirkham

docs/develop/json-manifest-overview.md

@@ -10,8 +10,7 @@ ms.localizationpriority: high
 
 This article is intended to help readers who are familiar with the add-in only manifest understand the unified manifest by comparing the two. Readers should also see [Office Add-ins with the unified manifest for Microsoft 365](unified-manifest-overview.md).
 
-> [!NOTE]
-> The unified manifest currently only supports Outlook add-ins and only in Office linked to a Microsoft 365 subscription and installed on Windows, on a mobile device, or in Outlook on the web. We're working on extending support to Excel, PowerPoint, and Word, as well as to Outlook on Mac, and to perpetual versions of Office.
+[!include[Unified manifest host application support note](../includes/unified-manifest-support-note.md)]
 
 ## Schemas and general points
 

docs/develop/unified-manifest-overview.md

@@ -21,10 +21,7 @@ One important improvement is the ability to create a single unit of distribution
 
 We've taken an important first step toward these goals by making it possible for you to create Outlook add-ins with a unified manifest for Microsoft 365.
 
-> [!NOTE]
->
-> - The unified manifest currently only supports Outlook add-ins and only in Office linked to a Microsoft 365 subscription and installed on Windows, on a mobile device, or in Outlook on the web. We're working on extending support to Excel, PowerPoint, and Word, as well as to Outlook on Mac, and to perpetual versions of Office.
-> - The unified manifest requires Office Version 2304 (Build 16320.00000) or later.
+[!include[Unified manifest host application support note](../includes/unified-manifest-support-note.md)]
 
 > [!TIP]
 > Ready to get started with the unified manifest? Begin with [Build an Outlook add-in with the unified manifest for Microsoft 365](../quickstarts/outlook-quickstart-json-manifest.md).

docs/includes/manifest-guidance.md

@@ -1,7 +1,12 @@
 > [!TIP]
 > If you'll be testing your add-in across multiple environments (for example, in development, staging, demo, etc.), we recommend that you maintain a different manifest file for each environment. In each manifest file, you can:
+> 
 > - Specify the URLs that correspond to the environment.
-> - Customize metadata values like `DisplayName` and labels within `Resources` to indicate the environment, so that end users will be able to identify a sideloaded add-in's corresponding environment. 
+> - Customize metadata values so that end users are able to identify a sideloaded add-in's corresponding environment. For example:
+>
+>    - In the unified manifest for Microsoft 365, customize the "name" property of the add-in and the "label" properties for various UI controls to indicate the environment.
+>    - In the add-in only manifest, customize the `DisplayName` element and and labels within the `Resources` element to indicate the environment. 
+>
 > - Customize the custom functions `namespace` to indicate the environment, if your add-in defines custom functions.
 > 
 > By following this guidance, you'll streamline the testing process and avoid issues that would otherwise occur when an add-in is simultaneously sideloaded for multiple environments.

docs/includes/unified-manifest-support-note.md

@@ -1,2 +1,2 @@
 > [!NOTE]
-> The [unified manifest for Microsoft 365](../develop/unified-manifest-overview.md) can be used in production Outlook add-ins. It's available only as a preview for Excel, PowerPoint, and Word add-ins. 
+> The [unified manifest for Microsoft 365](../develop/unified-manifest-overview.md) can be used in production Outlook add-ins. It's available only as a preview for Excel, PowerPoint, and Word add-ins.