chore: Some broken links

docs/src/main/paradox/durable-state.md

@@ -43,7 +43,7 @@ The table below shows the `akka-projection-durable-state` direct dependencies.Th
 ## SourceProvider for changesByTag
 
 A @apidoc[SourceProvider] defines the source of the envelopes that the `Projection` will process. A `SourceProvider`
-for the `changes` query can be defined with the @apidoc[DurableStateStoreProvider$] like this:
+for the `changes` query can be defined with the @apidoc[DurableStateStoreProvider] like this:
 
 Scala
 :  @@snip [DurableStateStoreDocExample.scala](/examples/src/test/scala/docs/state/DurableStateStoreDocExample.scala) { #changesByTagSourceProvider }
@@ -63,7 +63,7 @@ by the `Projection`. See @apidoc[akka.persistence.query.DurableStateChange] for
 ## SourceProvider for changesBySlices
 
 A @apidoc[SourceProvider] defines the source of the envelopes that the `Projection` will process. A `SourceProvider`
-for the `changesBySlices` query can be defined with the @apidoc[DurableStateStoreProvider$] like this:
+for the `changesBySlices` query can be defined with the @apidoc[DurableStateStoreProvider] like this:
 
 Scala
 :  @@snip [DurableStateStoreDocExample.scala](/examples/src/test/scala/docs/state/DurableStateStoreDocExample.scala) { #changesBySlicesSourceProvider }

docs/src/main/paradox/eventsourced.md

@@ -97,4 +97,4 @@ and loading of events from the database.
 
 `EventsBySliceFirehoseQuery` is used in place of `EventsBySliceQuery` with the `EventSourcedProvider`.
 
-It is typically used together with @extref:[Sharded Daemon Process with colocated processes](akka:typed/cluster-sharded-daemon-process.md#colocate-processes).
+It is typically used together with @extref:[Sharded Daemon Process with colocated processes](akka:typed/cluster-sharded-daemon-process.html#colocate-processes).

docs/src/main/paradox/grpc-producer-push.md

@@ -91,7 +91,7 @@ This can be used together with the additional producer metadata to add authentic
 ## Producer set up
 
 The producer is essentially a special projection handler for a projection running on the producer. It could be a single actor system
-running one projection handling all slices, or it could be @extref:[Sharded Daemon Process](akka:typed/cluster-sharded-daemon-process.md)
+running one projection handling all slices, or it could be @extref:[Sharded Daemon Process](akka:typed/cluster-sharded-daemon-process.html)
 pushing events for partitioned slices of the entities.
 
 The producer is created through @apidoc[EventProducerPush], which has a method `handler()` which returns a handler to be plugged into 

docs/src/main/paradox/grpc-replicated-event-sourcing-transport.md

@@ -6,8 +6,8 @@ such as active-active and hot standby.
 
 Originally, Akka Replicated Event Sourcing has required cross-replica access to the underlying replica database, which
 can be hard to open up for security and infrastructure reasons. It was also easiest to use in an
-[Akka Multi DC Cluster](https://doc.akka.io/libraries/akka-core/current/typed/cluster-dc.html) setup
-where a single cluster spans multiple datacenters or regions, another thing that can be complicated to allow.
+Akka Multi DC Cluster setup where a single cluster spans multiple datacenters or regions, another
+thing that can be complicated to allow.
 
 Akka Replicated Event Sourcing over gRPC builds on @ref:[Akka Projection gRPC](grpc.md) and @extref:[Akka gRPC](akka-grpc:index.html) to instead use gRPC as the cross-replica transport for events.
 

docs/src/main/paradox/r2dbc.md

@@ -248,7 +248,7 @@ Same type of handlers can be used with `R2dbcProjection` instead of `CassandraPr
 ### Actor handler
 
 A good alternative for advanced state management is to implement the handler as an
-@extref:[actor](akka:typed/typed/actors.html) which is described in
+@extref:[actor](akka:typed/actors.html) which is described in
 @ref:[Processing with Actor](actor.md).
 
 ### Flow handler

docs/src/main/paradox/snapshots.md

@@ -3,7 +3,7 @@ project.description: Snapshot builds of Akka Projection.
 ---
 # Snapshots
 
-Snapshots are published to https://repo.akka.io/snapshots repository after every successful build on main.
+Snapshots are published to https://repo.akka.io/snapshots/ repository after every successful build on main.
 Add the following to your project build definition to resolve Akka Projection's snapshots:
 
 ## Configure repository

scripts/link-validator.conf

@@ -27,6 +27,8 @@ site-link-validator {
     "https://github.com/"
     # MVN repository forbids access after a few requests
     "https://mvnrepository.com/artifact/"
+    # link checker is using HEAD requests, which isn't supported by the repo index
+    "https://repo.akka.io/snapshots"
   ]
 
   non-https-whitelist = [