Incorrect link for tenant specific app registrations (#1927)

The link to the PnP PowerShell page was not working so updated to point to https://pnp.github.io/powershell/articles/registerapplication

content/post/changes-pnp-management-shell-registration/index.md

@@ -51,7 +51,7 @@ If you have any questions, please use the specific issue list(s) for the questio
 
 Here's the specific guidance for the PnP PowerShell and CLI for Microsoft 365 to use tenant specific app registration.
 
-* **PnP PowerShell** - [Connect using your own Entra ID Application](https://pnp.github.io/powershell/articles/connecting.html#connect-by-using-your-own-entra-id-application)
+* **PnP PowerShell** - [Connect using your own Entra ID Application](https://pnp.github.io/powershell/articles/registerapplication)
 * **CLI for Microsoft 365** - [Using your own Microsoft Entra identity](https://pnp.github.io/cli-microsoft365/user-guide/using-own-identity/)
 
 Here are also guidance videos on how to get started with the PnP PowerShell and CLI for Microsoft 365 in single tenant registration
@@ -67,4 +67,4 @@ We are following up on the updated focus for customer security across the ecosys
 This depends. Change will impact authentication flow on every script which has been using the multi-tenant app registration pattern. Please double check the authentication model you are using and update accordingly. Otherwise, there will not be any changes required for the scripts.
 
 **Will existing scripts work after the authentication is changed with single tenant app registration?**
-Yes. You'll need to potentially update the authentication/connections section, but otherwise all the cmdlets and commands are working similarly with the multi-tenant and single tenant app registrations.
+Yes. You'll need to potentially update the authentication/connections section, but otherwise all the cmdlets and commands are working similarly with the multi-tenant and single tenant app registrations.