Docs: Fix invalid paths

docs/api/index.md

@@ -11,7 +11,6 @@ Full API reference documentation on Akka.NET's modules, classes, and APIs.
 * [Akka.Streams API Docs](Akka.Streams.yml)
 * [Akka.Cluster API Docs](Akka.Cluster.yml)
 * [Akka.Cluster.Sharding API Docs](Akka.Cluster.Sharding.yml)
-* [Akka.Cluster.Tools API Docs](Akka.Cluster.Tools.yml)
 * [Akka.DependencyInjection API Docs](Akka.DependencyInjection.yml)
 * [Akka.Discovery API Docs](Akka.Discovery.yml)
 

docs/articles/persistence/custom-persistence-provider.md

@@ -444,7 +444,7 @@ There are two conventions that needs to be implemented when you extend `IExtensi
 
 * It is strongly recommended to create a static `Get` method that returns an instance of this class. This method is responsible for registering the extension with the Akka.NET extension manager and instantiates a new instance for users to use.
 
-[!code-csharp[Get-Instance](../../../src/examples/Akka.Persistence.Custom/SqlitePersistence.cs?name=Get-Instance "Extension static Get method")]
+[!code-csharp[GetInstance](../../../src/examples/Akka.Persistence.Custom/SqlitePersistence.cs?name=GetInstance "Extension static Get method")]
 
 ### Extending `ExtensionIdProvider<T>`
 

docs/articles/remoting/performance.md

@@ -114,7 +114,7 @@ You can achieve similar results for your application.
 
 #### Optimizing Batches for Your Use Case
 
-To take advantage of I/O batching in DotNetty, you need to [tailor the following Akka.Remote configuration values to your use case](../../configuration/modules/akka.remote.md):
+To take advantage of I/O batching in DotNetty, you need to [tailor the following Akka.Remote configuration values to your use case](../../articles/configuration/modules/akka.remote.md):
 
 ```hocon
 akka.remote.dot-netty.tcp{

docs/articles/testing/multi-node-testing-old.md

@@ -52,7 +52,7 @@ The first step in creating an effective multi-node test is to define the configu
 
 The declaration of the `RoleName` properties is what the MNTR uses to determine how many nodes will be participating in this test. In this example, the test will create exactly two test processes.
 
-The `CommonConfig` element of the [`MultiNodeConfig` implementation class](../../api/Akka.Remote.TestKit.MultiNodeConfig.md) is the common config that will be used throughout all of the nodes inside the multi-node test. So, for instance, if you want all of the nodes in your test to run [Akka.Cluster.Sharding](xref:cluster-sharding) you'd want to include those configuration elements inside the `CommonConfig` property.
+The `CommonConfig` element of the [`MultiNodeConfig` implementation class](../../api/Akka.Remote.TestKit.MultiNodeConfig.html) is the common config that will be used throughout all of the nodes inside the multi-node test. So, for instance, if you want all of the nodes in your test to run [Akka.Cluster.Sharding](xref:cluster-sharding) you'd want to include those configuration elements inside the `CommonConfig` property.
 
 #### Configuring Individual Nodes Differently
 

docs/articles/testing/multi-node-testing.md

@@ -57,7 +57,7 @@ The first step in creating an effective multi-node test is to define the configu
 
 The declaration of the `RoleName` properties is what the MNTR uses to determine how many nodes will be participating in this test. In this example, the test will create exactly two test processes.
 
-The `CommonConfig` element of the [`MultiNodeConfig` implementation class](../../api/Akka.Remote.TestKit.MultiNodeConfig.md) is the common config that will be used throughout all of the nodes inside the multi-node test. So, for instance, if you want all of the nodes in your test to run [Akka.Cluster.Sharding](xref:cluster-sharding) you'd want to include those configuration elements inside the `CommonConfig` property.
+The `CommonConfig` element of the [`MultiNodeConfig` implementation class](../../api/Akka.Remote.TestKit.MultiNodeConfig.html) is the common config that will be used throughout all of the nodes inside the multi-node test. So, for instance, if you want all of the nodes in your test to run [Akka.Cluster.Sharding](xref:cluster-sharding) you'd want to include those configuration elements inside the `CommonConfig` property.
 
 #### Configuring Individual Nodes Differently
 

src/common.props

@@ -2,7 +2,7 @@
   <PropertyGroup>
     <Copyright>Copyright © 2013-2021 Akka.NET Team</Copyright>
     <Authors>Akka.NET Team</Authors>
-    <VersionPrefix>1.4.33</VersionPrefix>
+    <VersionPrefix>1.4.34</VersionPrefix>
     <PackageIcon>akkalogo.png</PackageIcon>
     <PackageProjectUrl>https://github.com/akkadotnet/akka.net</PackageProjectUrl>
     <PackageLicenseUrl>https://github.com/akkadotnet/akka.net/blob/master/LICENSE</PackageLicenseUrl>

src/contrib/testkits/Akka.TestKit.Xunit/Internals/AkkaAssertEqualityComparer.cs

@@ -13,7 +13,7 @@
 namespace Akka.TestKit.Xunit.Internals
 {
     /// <summary>
-    /// Default implementation of IEqualityComparer<T> used by the Akka's xUnit.net equality assertions.
+    /// Default implementation of IEqualityComparer{T} used by the Akka's xUnit.net equality assertions.
     /// Copy of xUnits code
     /// https://github.com/xunit/xunit/blob/3e6ab94ca231a6d8c86e90d6e724631a0faa33b7/src/xunit.assert/Asserts/Sdk/AssertEqualityComparer.cs
     /// <remarks>Note! Part of internal API. Breaking changes may occur without notice. Use at own risk.</remarks>

src/examples/Akka.Persistence.Custom/SqlitePersistence.cs

@@ -23,12 +23,12 @@ public static Config DefaultConfiguration()
             return ConfigurationFactory.FromResource<SqlitePersistence>("Akka.Persistence.Custom.sqlite.conf");
         }
 
-        // <Get-Instance>
+        // <GetInstance>
         public static SqlitePersistence Get(ActorSystem system)
         {
             return system.WithExtension<SqlitePersistence, SqlitePersistenceProvider>();
         }
-        // </Get-Instance>
+        // </GetInstance>
 
         /// <summary>
         /// Journal-related settings loaded from HOCON configuration.