From 9c9fcdf5706e20fe33be8f4b167a1ab4a2db2efc Mon Sep 17 00:00:00 2001 From: Sam Erde Date: Mon, 9 Dec 2024 11:32:47 -0500 Subject: [PATCH] typos --- _posts/2024-12-09-Revisiting-Join-Path-in-PowerShell.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2024-12-09-Revisiting-Join-Path-in-PowerShell.markdown b/_posts/2024-12-09-Revisiting-Join-Path-in-PowerShell.markdown index b5171d642279..a7d62dc78569 100644 --- a/_posts/2024-12-09-Revisiting-Join-Path-in-PowerShell.markdown +++ b/_posts/2024-12-09-Revisiting-Join-Path-in-PowerShell.markdown @@ -29,7 +29,7 @@ Join-Path You may not have realized that it supports wildcards in the parent and child paths, and can return an array of strings that represent paths. ```powershell -Join-Path -Path "$Home\AppData\Local*" -ChildPath "Microsoft*" -Resolve" +Join-Path -Path "$Home\AppData\Local*" -ChildPath "Microsoft*" -Resolve ``` ![A screen shot of PowerShell in Windows Terminal running the command 'Join-Path -Path "$Home\AppData\Local*" -ChildPath "Microsoft*" -Resolve'.](https://samerde.github.io/assets/img/content/Join-Path-Wildcards.png) @@ -39,7 +39,7 @@ Join-Path -Path C:\, C:\Windows, $env:LOCALAPPDATA -ChildPath "Temp" -Resolve ``` ![A screen shot of PowerShell in Windows Terminal running an example of Join-Path with multiple parent paths.](https://samerde.github.io/assets/img/content/Join-Path-Multiple-Parents.png) -The difference between Windows PowerShell and PowerShell becomes apparent when you want to join more than one child path. PowerShell added the **AditionalPath** parameter, which allows you to add virtually unlimited child paths like this: +The difference between Windows PowerShell and PowerShell becomes apparent when you want to join more than one child path. PowerShell added the **AdditionalPath** parameter, which allows you to add virtually unlimited child paths like this: ```powershell # Join multiple child paths in PowerShell