Simplify upgrade guide by removing redundant step.

Removed the section on verifying Data Protection configuration, as it was overly detailed and not directly relevant to the IdentityServer upgrade process. This streamlines the instructions, making them clearer and easier to follow.

Author: khalidabuhakmeh

IdentityServer/v7/docs/content/upgrades/v7.1_to_v7.2.md

@@ -32,9 +32,7 @@ would change to:
 <PackageReference Include="Duende.IdentityServer" Version="7.2.0" />
 ```
 
-## Step 2: Verify Data Protection Configuration
-IdentityServer depends on ASP.NET Data Protection. Data Protection encrypts and signs data using keys managed by ASP.NET. Those keys are isolated by application name, which by default is set to the content root path of the host. This prevents multiple applications from sharing encryption keys, which is necessary to protect your encryption against certain forms of attack. However, this means that if your content root path changes, the default settings for data protection will prevent you from using your old keys. Beginning in .NET 6, the content root path was normalized so that it ends with a directory separator. In .NET 7 that change was reverted. This means that your content root path might change if you upgrade from .NET 6 to .NET 7. This can be mitigated by explicitly setting the application name and removing the separator character. See [Microsoft's documentation for more information](https://learn.microsoft.com/en-us/aspnet/core/security/data-protection/configuration/overview?view=aspnetcore-7.0#setapplicationname).
 
-## Step 3: Done!
+## Step 2: Done!
 
 That's it. Of course, at this point you can and should test that your IdentityServer is updated and working properly.