Fixed typos and grammar on multiple posts

Author: PsCustomObject

_posts/2018-12-24-Add-Remove-Items-From-Array.md

@@ -29,7 +29,7 @@ $adUsers = Get-AdUser -Filter '*' -Server $adDomainController
 
 The above will return an array of AD objects containing all users matching the used filter.
 
-Of course you can initialize an empty array with the following syntax
+Of course you can initialise an empty array with the following syntax
 
 ```powershell
 $myArray = @()
@@ -38,7 +38,7 @@ $myArray = @()
 [array]$myArray = @()
 ```
 
-The above will initialize an empty array that we can, for example, fill with an AD query or adding static elements like this
+The above will initialise an empty array that we can, for example, fill with an AD query or adding static elements like this
 
 ```powershell
 $myArray = (1,2,3,4,5)

_posts/2018-12-27-PowerShell-Delete-Files-Older-Than-Days.md

@@ -73,7 +73,7 @@ foreach ($file in $filesToPurge)
 }
 ```
 
-The above code has an issue though. Maybe no file in defined folder is older that the define time span period while this would not generate any error it is a good idea to add a small clause to our code like this:
+The above code has an issue though. Maybe no file in defined folder is older that the defined time span period while this would not generate any error it is a good idea to add a small clause to our code like this:
 
 ```powershell
 if ($filesToPurge.Count -gt 0)
@@ -108,7 +108,7 @@ There are probably more features that could make the script even more useful and
 
 I am developing something to accommodate the above requirements as it is something I do rather frequently, it is not quite ready yet but I will share as soon code has been written and tested.
 
-## Update January 5th 2019
+## Update January 5 2019
 
 I have released a complete solution to perform automatic cleanup of files in folders called **Remove-OldFiles.ps1** it does all that I described in the post in addition to support:
 

_posts/2019-09-08-PowerShell-Convert-to-Title-Case.md

@@ -42,7 +42,7 @@ $firstString -eq $SecondString
 $true
 ```
 
-Most of the times this is not an issue but there are cases, for example when generating DisplayNames for users, where you want to *sanitize* the string so that it will use proper **Title Case**.
+Most of the times this is not an issue but there are cases, for example when generating DisplayNames for users, where you want to *sanitise* the string so that it will use proper **Title Case**.
 
 ## PowerShell convert string to Title Case
 

_posts/2019-10-28-Measure-Script-Time.md

@@ -11,7 +11,6 @@ tags:
   - PowerShell Timer
   - PowerShell StopWatch
   - StopWatch how-to
-  - PowerShell measure
   - PowerShell Execution Time
 ---
 
@@ -71,7 +70,7 @@ I use, *abuse* would be a better fit, the **Get-Date** cmdlet and measuring scri
 Write-Host $($startMs - $endMs)
 ```
 
-In the above example we initialize a variable containing begin of operation milliseconds, again have PowerShell count from 1 to 10000, set another variable at the end of the cycle and finally print out difference between the start and end time giving us elapsed milliseconds.
+In the above example we initialise a variable containing begin of operation milliseconds, again have PowerShell count from 1 to 10000, set another variable at the end of the cycle and finally print out difference between the start and end time giving us elapsed milliseconds.
 
 **Warning Notice:** I personally discourage, and never use myself, this approach for different reasons. *First* it makes code more difficult to read and generally **slower** due use of multiple variables and extra calculation. *Second* it poses problems with the elapsed time itself, what if the example above  would require 5 seconds to execute? Would it still work according to you?
 {: .notice--warning}

_posts/2020-08-04-PowerShell-Export-Registry-Key.md

@@ -12,7 +12,7 @@ header:
     teaser: "/assets/images/WindowsRegistry.png"
 ---
 
-Window registry has been for many years the joy and pain of every Windows Systems Administrator and if memory does not fail me it was even part of some of the old NT4 exams (the sweet sting of nostalgia!)
+Window registry has been for many years the joy and pain of every Windows Systems Administrator and if memory does not fail me it was even part of some of the old NT4 exams (the sweet sting of nostalgia!).
 
 ![MCSE Windows NT](/assets/images/WindowsNTBook.jpg)
 

_posts/2020-08-11-PowerShell-Get-Users-Manager.md

@@ -200,7 +200,7 @@ function Get-ReportChain
 }
 ```
 
-Function accepts **SamAccountName**, **UserPrincipalName** or **DistinguishedName** of a user account and will reutrn an array containing all direct and indirect reports of the user.
+Function accepts **SamAccountName**, **UserPrincipalName** or **DistinguishedName** of a user account and will return an array containing all direct and indirect reports of the user.
 
 ```powershell
 # Get reports for user

_posts/2022-01-25-Cannot bind argument to parameter-Token-Expiry.md

@@ -49,7 +49,7 @@ It took me quite a bit to figure this out as no exception during the connection
 When I was about to give up and open a ticket with Microsoft, which is usually as helpful as freezer in the North Pole, I discovered by chance that opening connection to Exchange Online **first** and **only afterwards** to the Exchange on-prem was working as intended, allowing me to interact with both the Online service and my local Exchange.
 
 **Note:** I have experienced/tested this with version 2.0.4 and 2.0.5 of Exchange Online PowerShell module but other versions could be affected as well.
-{: .notice—-warning}
+{: .notice--warning}
 
 I did not dig deep into the root cause of the issue but plan to do this tomorrow and already sent my feedback to exocmdletpreview {at} service {fullstop} microsoft {fullstop} com but I doubt I will hear anything from that channel. I plan to open a ticket anyhow to at least have an official statement on this.