Refine documentation for clarity and consistency

Updated links, clarified terminology, and improved formatting for better readability. Adjusted code and text references to align with standard conventions and enhance user understanding.

Author: khalidabuhakmeh

src/content/docs/identitymodel/endpoints/dynamic-registration.md

@@ -9,7 +9,8 @@ redirect_from:
 ---
 
 The client library for [OpenID Connect Dynamic Client Registration](https://openid.net/specs/openid-connect-registration-1_0.html)
-is provided as an extension method for *HttpClient*.
+is provided as an extension method for [
+`System.Net.Http.HttpClient`](https://learn.microsoft.com/en-us/dotnet/api/system.net.http.httpclient).
 
 The following code sends a registration request:
 

src/content/docs/identityserver/ui/login/dynamicproviders.md

@@ -10,7 +10,7 @@ redirect_from:
 ---
 
 Dynamic Identity Providers are a scalable solution for managing authentication with lots of external providers, without
-incurring performance penalties or requiring application recompilation. This feature, included in the Enterprise Edition
+incurring performance penalties or requiring application recompilation. This feature, included in the [Enterprise Edition](/general/licensing/#enterprise-edition)
 of Duende IdentityServer, enables providers to be configured dynamically from a store at runtime.
 
 ## Dynamic Identity Providers
@@ -76,7 +76,7 @@ builder.Services
 The identity provider store only provides an interface to query dynamic providers and does not provide any methods to add, update, or delete identity providers.
 For custom store implementations, this means you'll need to implement a mechanism for populating the store with identity providers.
 
-If you're using the Entity Provider Core stored from the `Duende.IdentityServer.EntityFramework.Storage` NuGet package,
+If you're using the Entity Framework Core identity provider store from the `Duende.IdentityServer.EntityFramework.Storage` NuGet package,
 you can use the `ConfigurationDbContext` database context directly to add, update or remove dynamic identity providers:
 
 ```csharp title="SeedData.cs"
@@ -183,12 +183,12 @@ There are three paths that are set on the `OpenIdConnectOptions`:
 * [RemoteSignOutPath](https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.authentication.openidconnect.openidconnectoptions.remotesignoutpath).
   This is the OIDC front channel logout URI protocol value. The suffix `"/signout"` is used for this path.
 
-For your IdentityServer running at "https://sample.duendesoftware.com" and an OIDC identity provider whose
+For your IdentityServer running at `https://sample.duendesoftware.com` and an OIDC identity provider whose
 scheme is "idp1", your client configuration with the external OIDC identity provider would be:
 
-* The redirect URI would be "https://sample.duendesoftware.com/federation/idp1/signin"
-* The post logout redirect URI would be "https://sample.duendesoftware.com/federation/idp1/signout-callback"
-* The front channel logout URI would be "https://sample.duendesoftware.com/federation/idp1/signout"
+* The redirect URI would be `https://sample.duendesoftware.com/federation/idp1/signin`
+* The post logout redirect URI would be `https://sample.duendesoftware.com/federation/idp1/signout-callback`
+* The front channel logout URI would be `https://sample.duendesoftware.com/federation/idp1/signout`
 
 
 ## Advanced Configuration
@@ -411,9 +411,9 @@ Google authentication handler, a similar implementation detail may exist for the
 builder.Services.ConfigureOptions<OAuthPostConfigureOptions<GoogleOptions, GoogleHandler>>();
 ```
 
-### 4. Use Your Custom IdentityProvider
+### 4. Use A Custom IdentityProvider
 
-With these building blocks in place, you can start using your custom identity provider type with Duende IdentityServer
+With these building blocks in place, you can start using a custom identity provider type with Duende IdentityServer
 dynamic identity providers!
 
 ```csharp title="Program.cs"