update documentation

content/overview/introduction.md

@@ -20,27 +20,27 @@ It is useful in federated authentication (either with [WS-Federation](https://do
 
 ### EntraCP
 
-This is the [new version]({{< relref "/blog/announcing-entracp" >}}) that should be used on all the supported versions of SharePoint Server: SharePoint Subscription, SharePoint 2019 and SharePoint 2016.  
+This is the [new claims provider]({{< relref "/blog/announcing-entracp" >}}) to use on all the supported versions of SharePoint Server.  
 [Go to documentation]({{< relref "/docs/overview" >}}).
 
 ### AzureCP
 
-This is the legacy, deprecated version. You should use it only if you have SharePoint 2013, and [migrate otherwise]({{< relref "introduction#migrate-from-azurecp-to-entracp" >}}).  
+This is the legacy, deprecated claims provider, to use only with SharePoint 2013.  
 [Go to documentation]({{< relref "/docs-azurecp/overview" >}}).
 
 ## Should I migrate from AzureCP to EntraCP?
 
-Yes. Here are a few reasons why:
+Yes, you should:
 
-- AzureCP is deprecated and no longer maintained.
-- EntraCP uses the SharePoint solution type `Application` (instead of `Web Front End`), which makes administrative operations (install / update / delete) much easier and safer by design.
-- EntraCP has a much better design and uses the latest versions of the Nuget packages [Microsoft.Graph](https://www.nuget.org/packages/Microsoft.Graph/) and [Azure.Identity](https://www.nuget.org/packages/Azure.Identity), while AzureCP uses outdated, no longer maintained dependencies.
-- EntraCP has a single location to configure the proxy for all the SharePoint processes / servers in the farm.
+- AzureCP is no longer maintained and uses outdated, deprecated 3rd party libraries.
+- Administrative operations (install / update / delete) are much easier and safer in EntraCP, thanks to using the SharePoint solution type `Application` (instead of `Web Front End` in AzureCP).
+- EntraCP uses modern and up-to-date packages [Microsoft.Graph](https://www.nuget.org/packages/Microsoft.Graph/) and [Azure.Identity](https://www.nuget.org/packages/Azure.Identity).
+- EntraCP stores the proxy configuration directly, and it uses it in all SharePoint processes, in all the servers of the farm.
 
 ## Migrate from AzureCP to EntraCP
 
 There is no migration so to speak, because they are 2 completely different SharePoint solutions.  
-Below are the possible strategies to migrage to EntraCP.  
+There are 2 possible strategies discussed here, but be mindful that a claims provider is a critical component in a SharePoint farm, and any approach should be tested in a non-production environment first.
 
 ### Uninstall AzureCP, then install EntraCP
 
@@ -49,9 +49,9 @@ This strategy can be used if you are confident about all the steps involved.
 ### Install EntraCP side by side with AzureCP
 
 It is perfectly possible to have both claims providers installed on the same farm.  
-To switch from one claims provider to the other, all you need to do is update the property `ClaimProviderName` using the cmdlet `Get-SPTrustedIdentityTokenIssuer`.  
+Once both are installed, to switch from one to another, simply update the property `ClaimProviderName` from cmdlet `Get-SPTrustedIdentityTokenIssuer`.  
 
 At some point, you may decide to uninstall AzureCP, and this is where you need to be careful:  
-Some assemblies are used by both. Although it should not happen, it was reported a few times that uninstalling AzureCP removed the assemblies also used by EntraCP.  
+Some assemblies are used by both. Although it should not happen, it was reported a few times that uninstalling AzureCP removed assemblies also used by EntraCP.  
 If this happens, simply retract and redeploy EntraCP.wsp.  
 Unlike AzureCP, this operation is safe with EntraCP, and faster than finding out which assemblies got removed, and adding them back manually on each server.

hugo_stats.json

@@ -284,8 +284,6 @@
       "add-a-microsoft-entra-id-tenant",
       "add-a-new-tenant",
       "announcement",
-      "automated-installation",
-      "automated-uninstallation",
       "azurecp",
       "breaking-changes",
       "buttonColorMode",
@@ -319,8 +317,6 @@
       "install-entracp",
       "install-entracp-side-by-side-with-azurecp",
       "main-improvements",
-      "manual-installation",
-      "manual-uninstallation",
       "manually-create-the-missing-features",
       "migrate-from-azurecp-to-entracp",
       "nav-tab",