Fix broken and inconsistent documentation links in IdentityServer v8.0 upgrade guides and related reference docs.

Author: maartenba

astro/src/content/docs/identityserver/aspnet-identity/schemes.md

@@ -16,7 +16,7 @@ When a user logs in, their identity is established and persisted across requests
 
 When using IdentityServer without ASP.NET Identity, the default cookie scheme is named `"idsrv"`, though we recommend using the constant `IdentityServerConstants.DefaultCookieAuthenticationScheme` in your code if you ever need it.
 
-Starting in **v8.0**, the default cookie name (not the scheme name) has changed to `"__Host-idsrv"` to improve security. The scheme name remains `"idsrv"`. See [Cookie Name Migration (v8.0)](#cookie-name-migration-v80) below for upgrade instructions.
+Starting in **v8.0**, the default cookie name (not the scheme name) has changed to `"__Host-idsrv"` to improve security. The scheme name remains `"idsrv"`. See [Cookie Name Migration (v8.0)](#cookie-name-migration) below for upgrade instructions.
 
 The default cookie scheme is configured by default in `AddIdentityServer()`, which sets up the cookie authentication handler with this scheme name. This cookie is essential for:
 
@@ -59,7 +59,7 @@ This allows your login logic to read the claims from the external provider befor
 
 IdentityServer always uses the `"idsrv.external"` scheme here, available in the `IdentityServerConstants.ExternalCookieAuthenticationScheme` constant.
 
-Starting in **v8.0**, the default cookie _name_ for this scheme has changed to `"__Host-idsrv.external"` (previously `"idsrv.external"`). See [Cookie Name Migration (v8.0)](#cookie-name-migration-v80) below for upgrade instructions.
+Starting in **v8.0**, the default cookie _name_ for this scheme has changed to `"__Host-idsrv.external"` (previously `"idsrv.external"`). See [Cookie Name Migration (v8.0)](#cookie-name-migration) below for upgrade instructions.
 
 ### Check Session Cookie
 

astro/src/content/docs/identityserver/diagnostics/conformance-report.md

@@ -137,7 +137,7 @@ The HTML report displays:
 
 The conformance report uses `IClientStore.GetAllClientsAsync` to enumerate all clients for
 assessment. Custom `IClientStore` implementations must implement this method (added in v8.0).
-See the [upgrade guide](/identityserver/upgrades/v7_4-to-v8_0/#iclientstoregettallclientsasync-now-required)
+See the [upgrade guide](/identityserver/upgrades/v7_4-to-v8_0.md#iclientstoregetallclientsasync-now-required)
 for details.
 
 ## Full Example

astro/src/content/docs/identityserver/reference/stores/client-store.md

@@ -39,4 +39,4 @@ public interface IClientStore
 
 `GetAllClientsAsync` returns all configured clients as an async enumerable. <span data-shb-badge data-shb-badge-variant="default">Added in 8.0 (prerelease)</span>
 
-Used by the [conformance report](/identityserver/diagnostics/conformance-report/) and configuration validation features. Custom `IClientStore` implementations must implement this method — see the [upgrade guide](/identityserver/upgrades/v7_4-to-v8_0/#iclientstoregettallclientsasync-now-required) for details.
+Used by the [conformance report](/identityserver/diagnostics/conformance-report/) and configuration validation features. Custom `IClientStore` implementations must implement this method — see the [upgrade guide](/identityserver/upgrades/v7_4-to-v8_0.md#iclientstoregetallclientsasync-now-required) for details.

astro/src/content/docs/identityserver/upgrades/v7_4-to-v8_0.md

@@ -164,7 +164,7 @@ If you are not using the SAML 2.0 feature, no schema changes are required.
 #### Custom Store Implementations
 
 If your IdentityServer implementation uses a custom `IClientStore`, you must add the new
-`GetAllClientsAsync` method (see [Breaking Change 4f](#iclientstoregettallclientsasync-now-required)
+`GetAllClientsAsync` method (see [Breaking Change](#iclientstoregetallclientsasync-now-required)
 below).
 
 #### Duende.IdentityServer.EntityFramework