Fixed typo in article

Renamed article .MD file
Fixed typo in syntax

Author: PsCustomObject

…nd argument to parameter-Token-Expiry.md …nd argument to parameter-Token-Expiry.md_posts/2022-01-25-annot bind argument to parameter-Token-Expiry.md renamed to _posts/2022-01-25-Cannot bind argument to parameter-Token-Expiry.md _posts/2022-01-25-annot bind argument to parameter-Token-Expiry.md renamed to _posts/2022-01-25-Cannot bind argument to parameter-Token-Expiry.md

@@ -18,23 +18,23 @@ header:
 
 ## Exchange Online Certificate Based authentication
 
-Microsoft is, *finally*, disabling **basic authentication** (read username and password) in Exchange Online in favour of **Certificate Based authentication**.
+Microsoft is, _finally_, disabling **basic authentication** (read username and password) in Exchange Online in favour of **Certificate Based authentication**.
 
-Once this change is fully implemented, around mid February at least for some tenants, connecting via username and passwords to Exchange Online will not be possible anymore. 
+Once this change is fully implemented, around mid February at least for some tenants, connecting via username and passwords to Exchange Online will not be possible anymore.
 
-You can read my article on how to implement *Certificate Based authentication*  for Exchange Online [here](https://pscustomobject.github.io/powershell/office365/exchange/Exchange-Online-Certificate-Based-Authentication/).
+You can read my article on how to implement _Certificate Based authentication_ for Exchange Online [here](https://pscustomobject.github.io/powershell/office365/exchange/Exchange-Online-Certificate-Based-Authentication/).
 
-As a result of this change I started updating one of our automations, responsible for the whole lifecycle of our mailboxes, to ditch old credential objects in favour of the more secure Certificate Authentication. 
+As a result of this change I started updating one of our automations, responsible for the whole lifecycle of our mailboxes, to ditch old credential objects in favour of the more secure Certificate Authentication.
 
-This is when I encountered the *‌cannot bind argument to parameter 'token expiry time' because it is null.* error message.
+This is when I encountered the _‌cannot bind argument to parameter 'token expiry time' because it is null._ error message.
 
 ## Multiple PowerShell Exchange Sessions
 
-When operating an hybrid environment it is pretty common to open, in the same window/session, a PowerShell connection to both Exchange on-prem and Exchange online. 
+When operating an hybrid environment it is pretty common to open, in the same window/session, a PowerShell connection to both Exchange on-prem and Exchange online.
 
-This is required as part of the configuration, usually creation of the mailbox, takes place in on-prem for example via the *New-RemoteMailbox* cmdlet while other parts of the configuration are performed directly online.
+This is required as part of the configuration, usually creation of the mailbox, takes place in on-prem for example via the _New-RemoteMailbox_ cmdlet while other parts of the configuration are performed directly online.
 
-This morning while debugging my workflow I’ve noticed that while  trying to retrieve mailbox information from the on-prem server an exception was being thrown
+This morning while debugging my workflow I’ve noticed that while trying to retrieve mailbox information from the on-prem server an exception was being thrown
 
 ```powershell
 # Cmdlet I was running
@@ -46,12 +46,11 @@ Cannot bind argument to parameter 'token expiry time' because it is null.
 
 It took me quite a bit to figure this out as no exception during the connection phase was being thrown by either module.
 
-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. 
- 
+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. 
+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.
 
 As soon as I have any news I will update the post until then I hope you can find the information useful.
-