Fixes formatting and adds note.

Author: kenwith

repo_docs/NEW_CMDLETS.md

@@ -2,14 +2,16 @@
 **SECTION IN PROGRESS**
 
 1. Open PowerShell as Administrator.
-2. Import the module you want to document.
-- Skype for Business Online: https://technet.microsoft.com/en-us/library/dn362795(v=ocs.15).aspx
-- Microsoft Teams: https://blogs.technet.microsoft.com/skypehybridguy/2017/11/07/microsoft-teams-powershell-support/
-   Hint: Might need to use Upgrade-Module and also Uninstall-Module depending on version and if you already have a version installed.
-3. Use PlatyPS to generate Markdown.
-- Skype for Business Online: `New-MarkdownHelp -module tmp_byivwzpq.e1k -OutputFolder .\docs`.
-4. Find the new cmdlet and you will see the stubbed markdown.
-5. Add correct metadata, see other similar cmdlets for examples.
+1. Import the module you want to document.
+    - Skype for Business Online: https://technet.microsoft.com/en-us/library/dn362795(v=ocs.15).aspx
+    - Microsoft Teams: https://blogs.technet.microsoft.com/skypehybridguy/2017/11/07/microsoft-teams-powershell-support/
+    Hint: Might need to use Upgrade-Module and also Uninstall-Module depending on version and if you already have a version installed.
+1. Use PlatyPS to generate Markdown.
+    - Skype for Business Online: `New-MarkdownHelp -module tmp_byivwzpq.e1k -OutputFolder .\docs`.
+1. Find the new cmdlet and you will see the stubbed markdown.
+1. Add the correct Applicable tags to the top metadata and also the parameters for the cmdlet. 
+    See others for details. 
+    This is important since when the XML is generated to go back into the product the applicable is what is used for which content goes into which product.
 
     You will need to add the title and also applicable metadata for the cmdlet and also for each parameter.
 
@@ -38,21 +40,18 @@
     Accept wildcard characters: False
     ```
 
-6. Add the correct Applicable tags to the top metadata and also the parameters for the cmdlet. 
-    See others for details. 
-    This is important since when the XML is generated to go back into the product the applicable is what is used for which content goes into which product.
-7. Add the cmdlet to TOC. TOC file is the name of the module. 
-    For example, for all Skype cmdlets the TOC file is skype.md.
-8. Submit a Pull Request into the repo in appropriate place with adding the new cmdlet. aka.ms/office-powershell
 
+1. Add the cmdlet to TOC. TOC file is the name of the module. 
+    For example, for all Teams cmdlets the TOC file is teams.md.
+    You can fill in a description or remove the template text line.
+    However, if you leave the template text line make sure it is exactly in the right format so that it will not render as a template text.
+1. Submit a Pull Request into the repo in appropriate place with adding the new cmdlet. aka.ms/office-powershell
 
 
-If you want to merge multiple versions into a single version then use the PlatyPS merge command.
-
-Make sure to update the TOC file. Exact format required so that the template text doesn't show up.
 
-Add metadata to the file so it shows in the correct reports. See these scripts to do it or you can do it manually too.
+If you want to merge multiple versions into a single version then use the PlatyPS merge command.
 
+Note: If this is a brand new product you need to add metadata at the global level in order for it to show up in reporting.
 
 References:
 https://docs.microsoft.com/en-us/powershell/module/powershellget/install-module?view=powershell-6