Fixes #10898 - Add note about AdditionalChildPath parameter (#10901)

* Add note about AdditionalChildPath parameter

* Apply suggestions from review

---------

Co-authored-by: Mikey Lombardi (He/Him) <[email protected]>

Author: sdwheeler

reference/5.1/Microsoft.PowerShell.Management/Join-Path.md

@@ -2,7 +2,7 @@
 external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml
 Locale: en-US
 Module Name: Microsoft.PowerShell.Management
-ms.date: 06/09/2017
+ms.date: 02/26/2024
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.management/join-path?view=powershell-5.1&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: Join-Path
@@ -38,7 +38,8 @@ path\childpath
 
 This command uses `Join-Path` to combine a path with a childpath.
 
-Since the command is executed from the `FileSystem` provider, it provides the `\` delimiter to join the paths.
+Since the command is executed from the `FileSystem` provider, it provides the `\` delimiter to join
+the paths.
 
 ### Example 2: Combine paths that already contain directory separators
 
@@ -50,17 +51,19 @@ PS C:\> Join-Path -Path "path\" -ChildPath "\childpath"
 path\childpath
 ```
 
-Existing directory separators `\` and handled so there is only one separator between `Path` and `ChildPath`
+Existing directory separators `\` are handled so there is only one separator between `Path` and
+`ChildPath`
 
 ### Example 3: Display files and folders by joining a path with a child path
 
 ```powershell
 Join-Path "C:\win*" "System*" -Resolve
 ```
 
-This command displays the files and folders that are referenced by joining the C:\Win\* path and the System\* child path.
-It displays the same files and folders as `Get-ChildItem`, but it displays the fully qualified path to each item.
-In this command, the `Path` and `ChildPath` optional parameter names are omitted.
+This command displays the files and folders that are referenced by joining the `C:\Win\*` path and
+the `System\*` child path. It displays the same files and folders as `Get-ChildItem`, but it
+displays the fully qualified path to each item. In this command, the `Path` and `ChildPath` optional
+parameter names are omitted.
 
 ### Example 4: Use Join-Path with the PowerShell registry provider
 
@@ -73,9 +76,11 @@ HKLM:\System\ControlSet001
 HKLM:\System\CurrentControlSet
 ```
 
-This command displays the registry keys in the `HKLM\System` registry subkey that include `ControlSet`.
+This command displays the registry keys in the `HKLM\System` registry subkey that include
+`ControlSet`.
 
-The `Resolve` parameter, attempts to resolve the joined path, including wildcards from the current provider path `HKLM:\`
+The `Resolve` parameter, attempts to resolve the joined path, including wildcards from the current
+provider path `HKLM:\`
 
 ### Example 5: Combine multiple path roots with a child path
 
@@ -106,20 +111,22 @@ C:\Subdir
 D:\Subdir
 ```
 
-This command combines the roots of each PowerShell file system drive in the console with the Subdir child path.
+This command combines the roots of each PowerShell file system drive in the console with the `Subdir`
+child path.
 
-The command uses the `Get-PSDrive` cmdlet to get the PowerShell drives supported by the FileSystem provider.
-The `ForEach-Object` statement selects only the Root property of the `PSDriveInfo` objects and combines it with the specified child path.
+The command uses the `Get-PSDrive` cmdlet to get the PowerShell drives supported by the FileSystem
+provider. The `ForEach-Object` statement selects only the **Root** property of the **PSDriveInfo**
+objects and combines it with the specified child path.
 
-The output shows that the PowerShell drives on the computer included a drive mapped to the C:\Program Files directory.
+The output shows that the PowerShell drives on the computer included a drive mapped to the
+`C:\Program Files` directory.
 
 ## PARAMETERS
 
 ### -ChildPath
 
-Specifies the elements to append to the value of the `Path` parameter.
-Wildcards are permitted.
-The `ChildPath` parameter is required, although the parameter name ("ChildPath") is optional.
+Specifies the elements to append to the value of the `Path` parameter. Wildcards are permitted. The
+`ChildPath` parameter is required, although the parameter name ("ChildPath") is optional.
 
 ```yaml
 Type: System.String
@@ -211,7 +218,10 @@ Accept wildcard characters: False
 
 ### CommonParameters
 
-This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
+-InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose,
+-WarningAction, and -WarningVariable. For more information, see
+[about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## INPUTS
 
@@ -227,18 +237,17 @@ This cmdlet returns a string that contains the resulting path.
 
 ## NOTES
 
-The cmdlets that contain the Path noun (the Path cmdlets) manipulate path names and return the
-names in a concise format that all PowerShell providers can interpret. They are designed for
-use in programs and scripts where you want to display all or part of a path name in a
-particular format. Use them like you would use Dirname, Normpath, Realpath, Join, or other path
-manipulators.
+The cmdlets that contain the Path noun (the Path cmdlets) manipulate path names and return the names
+in a concise format that all PowerShell providers can interpret. They are designed for use in
+programs and scripts where you want to display all or part of a path name in a particular format.
+Use them like you would use `Dirname`, `Normpath`, `Realpath`, `Join`, or other path manipulators.
 
 You can use the path cmdlets with several providers, including the `FileSystem`, `Registry`, and
 `Certificate` providers.
 
-This cmdlet is designed to work with the data exposed by any provider.
-To list the providers available in your session, type `Get-PSProvider`.
-For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
+This cmdlet is designed to work with the data exposed by any provider. To list the providers
+available in your session, type `Get-PSProvider`. For more information, see
+[about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
 
 ## RELATED LINKS
 

reference/7.2/Microsoft.PowerShell.Management/Join-Path.md

@@ -2,7 +2,7 @@
 external help file: Microsoft.PowerShell.Commands.Management.dll-Help.xml
 Locale: en-US
 Module Name: Microsoft.PowerShell.Management
-ms.date: 06/09/2017
+ms.date: 02/26/2024
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.management/join-path?view=powershell-7.2&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: Join-Path
@@ -39,6 +39,7 @@ path\childpath
 This command uses `Join-Path` to combine a path with a childpath.
 
 Since the command is executed from the `FileSystem` provider, it provides the `\` delimiter to join the paths.
+the paths.
 
 ### Example 2: Combine paths that already contain directory separators
 
@@ -50,17 +51,19 @@ PS C:\> Join-Path -Path "path\" -ChildPath "\childpath"
 path\childpath
 ```
 
-Existing directory separators `\` and handled so there is only one separator between `Path` and `ChildPath`
+Existing directory separators `\` are handled so there is only one separator between `Path` and
+`ChildPath`
 
 ### Example 3: Display files and folders by joining a path with a child path
 
 ```powershell
 Join-Path "C:\win*" "System*" -Resolve
 ```
 
-This command displays the files and folders that are referenced by joining the C:\Win\* path and the System\* child path.
-It displays the same files and folders as `Get-ChildItem`, but it displays the fully qualified path to each item.
-In this command, the `Path` and `ChildPath` optional parameter names are omitted.
+This command displays the files and folders that are referenced by joining the `C:\Win\*` path and
+the `System\*` child path. It displays the same files and folders as `Get-ChildItem`, but it
+displays the fully qualified path to each item. In this command, the `Path` and `ChildPath` optional
+parameter names are omitted.
 
 ### Example 4: Use Join-Path with the PowerShell registry provider
 
@@ -73,9 +76,11 @@ HKLM:\System\ControlSet001
 HKLM:\System\CurrentControlSet
 ```
 
-This command displays the registry keys in the `HKLM\System` registry subkey that include `ControlSet`.
+This command displays the registry keys in the `HKLM\System` registry subkey that include
+`ControlSet`.
 
-The `Resolve` parameter, attempts to resolve the joined path, including wildcards from the current provider path `HKLM:\`
+The `Resolve` parameter, attempts to resolve the joined path, including wildcards from the current
+provider path `HKLM:\`
 
 ### Example 5: Combine multiple path roots with a child path
 
@@ -106,12 +111,15 @@ C:\Subdir
 D:\Subdir
 ```
 
-This command combines the roots of each PowerShell file system drive in the console with the Subdir child path.
+This command combines the roots of each PowerShell file system drive in the console with the `Subdir`
+child path.
 
-The command uses the `Get-PSDrive` cmdlet to get the PowerShell drives supported by the FileSystem provider.
-The `ForEach-Object` statement selects only the Root property of the `PSDriveInfo` objects and combines it with the specified child path.
+The command uses the `Get-PSDrive` cmdlet to get the PowerShell drives supported by the FileSystem
+provider. The `ForEach-Object` statement selects only the **Root** property of the **PSDriveInfo**
+objects and combines it with the specified child path.
 
-The output shows that the PowerShell drives on the computer included a drive mapped to the C:\Program Files directory.
+The output shows that the PowerShell drives on the computer included a drive mapped to the
+`C:\Program Files` directory.
 
 ### Example 7: Combine an indefinite number of paths
 
@@ -138,6 +146,8 @@ parameter is still mandatory and must be specified as well.
 This parameter is specified with the `ValueFromRemainingArguments` property which enables
 joining an indefinite number of paths.
 
+This parameter was added in PowerShell 6.0.
+
 ```yaml
 Type: System.String[]
 Parameter Sets: (All)
@@ -152,9 +162,8 @@ Accept wildcard characters: False
 
 ### -ChildPath
 
-Specifies the elements to append to the value of the `Path` parameter.
-Wildcards are permitted.
-The `ChildPath` parameter is required, although the parameter name ("ChildPath") is optional.
+Specifies the elements to append to the value of the `Path` parameter. Wildcards are permitted. The
+`ChildPath` parameter is required, although the parameter name ("ChildPath") is optional.
 
 ```yaml
 Type: System.String
@@ -228,7 +237,10 @@ Accept wildcard characters: False
 
 ### CommonParameters
 
-This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
+-InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose,
+-WarningAction, and -WarningVariable. For more information, see
+[about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## INPUTS
 
@@ -244,18 +256,17 @@ This cmdlet returns a string that contains the resulting path.
 
 ## NOTES
 
-The cmdlets that contain the Path noun (the Path cmdlets) manipulate path names and return the
-names in a concise format that all PowerShell providers can interpret. They are designed for
-use in programs and scripts where you want to display all or part of a path name in a
-particular format. Use them like you would use Dirname, Normpath, Realpath, Join, or other path
-manipulators.
+The cmdlets that contain the Path noun (the Path cmdlets) manipulate path names and return the names
+in a concise format that all PowerShell providers can interpret. They are designed for use in
+programs and scripts where you want to display all or part of a path name in a particular format.
+Use them like you would use `Dirname`, `Normpath`, `Realpath`, `Join`, or other path manipulators.
 
 You can use the path cmdlets with several providers, including the `FileSystem`, `Registry`, and
 `Certificate` providers.
 
-This cmdlet is designed to work with the data exposed by any provider.
-To list the providers available in your session, type `Get-PSProvider`.
-For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
+This cmdlet is designed to work with the data exposed by any provider. To list the providers
+available in your session, type `Get-PSProvider`. For more information, see
+[about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md).
 
 ## RELATED LINKS
 
@@ -272,4 +283,3 @@ For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/a
 [Get-ChildItem](Get-ChildItem.md)
 
 [Get-PSDrive](Get-PSDrive.md)
-