Add include file pointing to PlatyPS docs (#10266)

* Add include file pointing to PlatyPS docs

* fix typo in URL

Author: sdwheeler

reference/docs-conceptual/developer/help/autogenerated-elements-of-comment-based-help.md

@@ -1,49 +1,47 @@
 ---
 description: Autogenerated Elements of Comment-Based Help
-ms.date: 09/12/2016
+ms.date: 07/10/2023
 ms.topic: reference
 title: Autogenerated Elements of Comment-Based Help
 ---
 # Autogenerated Elements of Comment-Based Help
 
 The `Get-Help` cmdlet automatically generates several elements of a comment-based topic. These
-autogenerated elements make comment-based help look very much like the help that is generated from
+autogenerated elements make comment-based help look very much like the help that's generated from
 XML files.
 
 ## Autogenerated Elements
 
-The `Get-Help` cmdlet automatically generates the following elements of a help topic. You cannot
-edit these elements directly, but in many cases you can change the results by changing the source of
-the element.
+The `Get-Help` cmdlet automatically generates the following elements of a help topic. You can't edit
+these elements directly, but you can change the results by changing the source of the element.
 
 ### Name
 
 The Name section of a function Help topic is taken from the function name in the function
-definition. The Name of a script Help topic is taken from the script filename. To change the name
-or its capitalization, change the function definition or the script filename.
+definition. The Name of a script Help topic is taken from the script filename. To change the name or
+its capitalization, change the function definition or the script filename.
 
 ### Syntax
 
 The Syntax section of the Help topic is generated from the parameter list in the Param statement of
 the function or script. To add detail to the Help topic syntax, such as the .NET type of a
-parameter, add the detail to the parameter list. If you do not specify a parameter type, the
+parameter, add the detail to the parameter list. If you don't specify a parameter type, the
 **Object** type is inserted as the default value.
 
 ### Parameter List
 
 The Parameters section of the Help topic is generated from the parameter list in the function or
-script and from the descriptions that you add by using the `.Parameters` keyword or comments in the
+script and from the descriptions that you add using the `.Parameters` keyword or comments in the
 parameter list.
 
 Parameters appear in the Parameters section in the same order that they appear in the parameter
 list. The spelling and capitalization of parameter names is also taken from the parameter list; it
-is not affected by the parameter name specified by the `.Parameter` keyword.
+isn't affected by the parameter name specified by the `.Parameter` keyword.
 
 ### Common Parameters
 
 The common parameters are added to the syntax and parameter list of the Help topic, even if they
-have no effect. For more information about the common parameters, see
-[about_CommonParameters](/powershell/module/microsoft.powershell.core/about/about_commonparameters).
+have no effect. For more information about the common parameters, see [about_CommonParameters][01].
 
 ### Parameter Attribute Table
 
@@ -54,4 +52,7 @@ value attributes is taken from the function or script syntax.
 ### Remarks
 
 The Remarks section of the Help topic is automatically generated from the function or script name.
-You cannot change or affect its content.
+You can't change or affect its content.
+
+<!-- link references -->
+[01]: /powershell/module/microsoft.powershell.core/about/about_commonparameters

reference/docs-conceptual/developer/help/comment-based-help-keywords.md

@@ -1,6 +1,6 @@
 ---
 description: Comment-Based Help Keywords
-ms.date: 02/03/2022
+ms.date: 07/10/2023
 ms.topic: reference
 no-loc: [FAQ, Function, General, Glossary, Provider, Component, Functionality, Role]
 title: Comment-Based Help Keywords
@@ -11,14 +11,13 @@ This topic lists and describes the keywords in comment-based help.
 
 ## Keywords in Comment-Based Help
 
-The following are valid comment-based Help keywords. They are listed in the order in which they
+The following are valid comment-based Help keywords. They're listed in the order in which they
 typically appear in a Help topic along with their intended use. These keywords can appear in any
-order in the comment-based Help, and they are not case-sensitive.
+order in the comment-based Help, and they're not case-sensitive.
 
 Note that the `.EXTERNALHELP` keyword takes precedence over all other comment-based help keywords.
-When `.EXTERNALHELP` is present, the
-[Get-Help](/powershell/module/Microsoft.PowerShell.Core/Get-Help) cmdlet does not display
-comment-based help, even when it cannot find a help file that matches the value of the keyword.
+When `.EXTERNALHELP` is present, the [Get-Help][02] cmdlet doesn't display comment-based help, even
+when it can't find a help file that matches the value of the keyword.
 
 ## `.SYNOPSIS`
 
@@ -73,7 +72,7 @@ version of the same Help topic. The online version opens when you use the `Onlin
 
 ## `.COMPONENT`
 
-The name of the technology or feature that the function or script uses, or to which it is related.
+The name of the technology or feature that the function or script uses, or to which it's related.
 The **Component** parameter of `Get-Help` uses this value to filter the search results returned by
 `Get-Help`.
 
@@ -121,27 +120,28 @@ keyword is used by the `Export-PSSession` cmdlet to find the Help topics for the
 
 Specifies the path and/or name of an XML-based Help file for the script or function.
 
-The `.EXTERNALHELP` keyword tells the
-[Get-Help](/powershell/module/Microsoft.PowerShell.Core/Get-Help) cmdlet to get help for the script
-or function in an XML-based file. The `.EXTERNALHELP` keyword is required when using an XML-based
-help file for a script or function. Without it, `Get-Help` will not find a help file for the
-function or script.
+The `.EXTERNALHELP` keyword tells the [Get-Help][02] cmdlet to get help for the script or function
+in an XML-based file. The `.EXTERNALHELP` keyword is required when using an XML-based help file for
+a script or function. Without it, `Get-Help` will not find a help file for the function or script.
 
 The `.EXTERNALHELP` keyword takes precedence over all other comment-based help keywords. When
-`.EXTERNALHELP` is present, the [Get-Help](/powershell/module/Microsoft.PowerShell.Core/Get-Help)
-cmdlet does not display comment-based help, even when it cannot find a help file that matches the
-value of the keyword.
+`.EXTERNALHELP` is present, the [Get-Help][02] cmdlet doesn't display comment-based help, even when
+it can't find a help file that matches the value of the keyword.
 
 When the function is exported by a script module, the value of `.EXTERNALHELP` should be a filename
 without a path. `Get-Help` looks for the file in a locale-specific subdirectory of the module
 directory. There are no requirements for the filename, but a best practice is to use the following
 filename format: `<ScriptModule>.psm1-help.xml`.
 
-When the function is not associated with a module, include a path and filename in the value of the
+When the function isn't associated with a module, include a path and filename in the value of the
 `.EXTERNALHELP` keyword. If the specified path to the XML file contains UI-culture-specific
 subdirectories, `Get-Help` searches the subdirectories recursively for an XML file with the name of
 the script or function in accordance with the language fallback standards established for Windows,
 just as it does for all XML-based Help topics.
 
 For more information about the cmdlet Help XML-based Help file format, see
-[Writing Windows PowerShell Cmdlet Help](./writing-help-for-windows-powershell-cmdlets.md).
+[Writing Windows PowerShell Cmdlet Help][01].
+
+<!-- link references -->
+[01]: ./writing-help-for-windows-powershell-cmdlets.md
+[02]: /powershell/module/Microsoft.PowerShell.Core/Get-Help

reference/docs-conceptual/developer/help/examples-of-comment-based-help.md

@@ -1,6 +1,6 @@
 ---
 description: Examples of Comment-Based Help
-ms.date: 01/11/2021
+ms.date: 07/10/2023
 ms.topic: reference
 title: Examples of Comment-Based Help
 ---
@@ -36,7 +36,7 @@ function Add-Extension
         Specifies the extension. "Txt" is the default.
 
         .INPUTS
-        None. You cannot pipe objects to Add-Extension.
+        None. You can't pipe objects to Add-Extension.
 
         .OUTPUTS
         System.String. Add-Extension returns a string with the extension or file name.
@@ -108,7 +108,7 @@ PS> Get-Help Add-Extension -full
                "get-help about_commonparameters".
 
         INPUTS
-            None. You cannot pipe objects to Add-Extension.
+            None. You can't pipe objects to Add-Extension.
 
         OUTPUTS
             System.String. Add-Extension returns a string with the extension or file name.
@@ -137,10 +137,10 @@ PS> Get-Help Add-Extension -full
 
 The following sample function includes comment-based Help.
 
-Notice the blank lines between the closing **#>** and the `Param` statement. In a script that does
-not have a `Param` statement, there must be at least two blank lines between the final comment in
-the Help topic and the first function declaration. Without these blank lines, `Get-Help` associates
-the Help topic with the function, instead of the script.
+Notice the blank lines between the closing `#>` and the `Param` statement. In a script that does not
+have a `Param` statement, there must be at least two blank lines between the final comment in the
+Help topic and the first function declaration. Without these blank lines, `Get-Help` associates the
+Help topic with the function, instead of the script.
 
 ```powershell
 <#
@@ -160,10 +160,10 @@ the Help topic with the function, instead of the script.
   saves the output in the local directory.
 
   .INPUTS
-  None. You cannot pipe objects to Update-Month.ps1.
+  None. You can't pipe objects to Update-Month.ps1.
 
   .OUTPUTS
-  None. Update-Month.ps1 does not generate any output.
+  None. Update-Month.ps1 doesn't generate any output.
 
   .EXAMPLE
   PS> .\Update-Month.ps1
@@ -180,8 +180,8 @@ param ([string]$InputPath, [string]$OutPutPath)
 function Get-Data { }
 ```
 
-The following command gets the script Help. Because the script is not in a directory that is listed
-in the Path environment variable, the `Get-Help` command that gets the script Help must specify the
+The following command gets the script Help. Because the script isn't in a directory that's listed in
+the Path environment variable, the `Get-Help` command that gets the script Help must specify the
 script path.
 
 ```powershell
@@ -231,10 +231,10 @@ PS> Get-Help c:\ps-test\update-month.ps1 -full
                    "get-help about_commonparameters".
 
             INPUTS
-                   None. You cannot pipe objects to Update-Month.ps1.
+                   None. You can't pipe objects to Update-Month.ps1.
 
             OUTPUTS
-                   None. Update-Month.ps1 does not generate any output.
+                   None. Update-Month.ps1 doesn't generate any output.
 
             -------------------------- EXAMPLE 1 --------------------------
 

reference/docs-conceptual/developer/help/file-types-permitted-in-an-updatable-help-cab-file.md

@@ -1,29 +1,31 @@
 ---
 description: File Types Permitted in an Updatable Help CAB File
-ms.date: 03/22/2012
+ms.date: 07/10/2023
 ms.topic: reference
 title: File Types Permitted in an Updatable Help CAB File
 ---
 # File Types Permitted in an Updatable Help CAB File
 
 Uncompressed CAB file content is limited to 1 GB by default. To bypass this limit, users have to use
-the **Force** parameter of the
-[Update-Help](/powershell/module/Microsoft.PowerShell.Core/Update-Help) and
-[Save-Help](/powershell/module/Microsoft.PowerShell.Core/Save-Help) cmdlets.
+the **Force** parameter of the [Update-Help][02] and [Save-Help][01] cmdlets.
 
 To assure the security of help files that are downloaded from the internet, an Updatable Help CAB
-file can include only the file types listed below. The
-[Update-Help](/powershell/module/Microsoft.PowerShell.Core/Update-Help) cmdlet validates all files
-against the help topic schemas. If the `Update-Help` cmdlet encounters a file that is invalid or is
-not a permitted type, it does not install the invalid file and stops installing files from the CAB
-on the user's computer.
+file can include only the file types listed below. The [Update-Help][02] cmdlet validates all files
+against the help topic schemas. If the `Update-Help` cmdlet encounters a file that's invalid or is
+not a permitted type, it doesn't install the invalid file and stops installing files from the CAB on
+the user's computer.
 
 - XML-based help topics for cmdlets.
 - XML-based help topics for scripts and functions.
 - XML-based help topics for PowerShell providers.
 - Text-based help topics, such as About topics.
 
-The [Update-Help](/powershell/module/Microsoft.PowerShell.Core/Update-Help) verifies the CAB
-contents when it unpacks the CAB. If `Update-Help` finds non-compliant file types in an Updatable
-Help CAB file, it generates a terminating error and stops the operation. It does not install any
-help files from the CAB, even those of compliant file types.
+The [Update-Help][02] verifies the CAB contents when it unpacks the CAB. If `Update-Help` finds
+non-compliant file types in an Updatable Help CAB file, it generates a terminating error and stops
+the operation. It doesn't install any help files from the CAB, even those of compliant file types.
+
+[!INCLUDE [use-platyps](../../../includes/use-platyps.md)]
+
+<!-- link references -->
+[01]: /powershell/module/Microsoft.PowerShell.Core/Save-Help
+[02]: /powershell/module/Microsoft.PowerShell.Core/Update-Help

reference/docs-conceptual/developer/help/helpinfo-xml-sample-file.md

@@ -1,19 +1,18 @@
 ---
 description: HelpInfo XML Sample File
-ms.date: 09/12/2016
+ms.date: 07/10/2023
 ms.topic: reference
 title: HelpInfo XML Sample File
 ---
 # HelpInfo XML Sample File
 
 This topic displays a sample of a well-formed Updatable Help Information file, commonly known as
 "HelpInfo XML file." In this sample file, the UI culture elements are arranged in alphabetical order
-by UI culture name. Alphabetical ordering is a best practice, but it is not required.
+by UI culture name. Alphabetical ordering is a best practice, but it's not required.
 
 ## HelpInfo XML Sample File
 
 ```xml
-
 <?xml version="1.0" encoding="utf-8"?>
 <HelpInfo xmlns="http://schemas.microsoft.com/powershell/help/2010/05">
    <HelpContentURI>https://go.microsoft.com/fwlink/?LinkID=141553</HelpContentURI>
@@ -36,5 +35,6 @@ by UI culture name. Alphabetical ordering is a best practice, but it is not requ
     </UICulture>
    </SupportedUICultures>
 </HelpInfo>
-
 ```
+
+[!INCLUDE [use-platyps](../../../includes/use-platyps.md)]

reference/docs-conceptual/developer/help/helpinfo-xml-schema.md

@@ -1,6 +1,6 @@
 ---
 description: HelpInfo XML Schema
-ms.date: 09/12/2016
+ms.date: 07/10/2023
 ms.topic: reference
 title: HelpInfo XML Schema
 ---
@@ -61,5 +61,10 @@ The HelpInfo XML file includes the following elements.
 
 - **UICultureVersion** - Contains a 4-part version number in "N1.N2.N3.N4" format that represents
   the version of the help CAB file in the UI culture. Increment this version number whenever you
-  upload new help CAB files in the UI culture that is specified by **UICultureName**. For more
-  information about this value, see [Version Class](/dotnet/api/system.version).
+  upload new help CAB files in the UI culture that's specified by **UICultureName**. For more
+  information about this value, see [Version Class][01].
+
+[!INCLUDE [use-platyps](../../../includes/use-platyps.md)]
+
+<!-- link references -->
+[01]: /dotnet/api/system.version

reference/docs-conceptual/developer/help/how-to-add-a-cmdlet-description.md

@@ -1,13 +1,15 @@
 ---
 description: How to Add a Cmdlet Description
-ms.date: 09/13/2016
+ms.date: 07/10/2023
 ms.topic: reference
 title: How to Add a Cmdlet Description
 ---
 # How to Add a Cmdlet Description
 
-This section describes how to add content that is displayed in the **DESCRIPTION** section of the cmdlet
-Help. In the Help file, this content is added to the **Command** node for each cmdlet.
+[!INCLUDE [use-platyps](../../../includes/use-platyps.md)]
+
+This section describes how to add content that's displayed in the **DESCRIPTION** section of the
+cmdlet Help. In the Help file, this content is added to the **Command** node for each cmdlet.
 
 > [!NOTE]
 > For a complete view of a Help file, open one of the `dll-Help.xml` files located in the PowerShell
@@ -35,9 +37,12 @@ Help. In the Help file, this content is added to the **Command** node for each c
   resource. The security descriptor contains the access control lists (ACLs) of the resource. The
   ACL specifies the permissions that users and user groups have to access the resource."
 
-- The detailed description should describe the cmdlet, but it should not describe concepts that the
+- The detailed description should describe the cmdlet, but it shouldn't describe concepts that the
   cmdlet uses. Place concept definitions in Additional Notes.
 
 ## See Also
 
-[Windows PowerShell SDK](../windows-powershell-reference.md)
+[Windows PowerShell SDK][01]
+
+<!-- link references -->
+[01]: ../windows-powershell-reference.md

reference/docs-conceptual/developer/help/how-to-add-a-see-also-section-to-a-provider-help-topic.md

@@ -1,11 +1,13 @@
 ---
 description: How to Add a See Also Section to a Provider Help Topic
-ms.date: 09/12/2016
+ms.date: 07/10/2023
 ms.topic: reference
 title: How to Add a See Also Section to a Provider Help Topic
 ---
 # How to Add a See Also Section to a Provider Help Topic
 
+[!INCLUDE [use-platyps](../../../includes/use-platyps.md)]
+
 This section explains how to populate the **SEE ALSO** section of a provider help topic.
 
 The **SEE ALSO** section consists of a list of topics that are related to the provider or might help
@@ -14,8 +16,8 @@ help and conceptual ("about") help topics in Windows PowerShell. It can also inc
 books, paper, and online topics, including an online version of the current provider help topic.
 
 When you refer to online topics, provide the URI or a search term in plain text. The `Get-Help`
-cmdlet does not link or redirect to any of the topics in the list. Also, the `Online` parameter of
-the `Get-Help` cmdlet does not work with provider help.
+cmdlet doesn't link or redirect to any of the topics in the list. Also, the `Online` parameter of
+the `Get-Help` cmdlet doesn't work with provider help.
 
 The **See Also** section is created from the `RelatedLinks` element and the tags that it contains.
 The following XML shows how to add the tags.
@@ -37,7 +39,7 @@ The following XML shows how to add the tags.
 
 1. For each topic in the **SEE ALSO** section, within the `RelatedLinks` element, add a
    `navigationLink` element. Then, within each `navigationLink` element, add one `linkText` element
-   and one `uri` element. If you are not using the `uri` element, you can add it as an empty element
+   and one `uri` element. If you aren't using the `uri` element, you can add it as an empty element
    (\<uri/>).
 
    For example: