diff --git a/src/Tests/Tests/ClientConcepts/Connection/ModifyingDefaultConnection.doc.cs b/src/Tests/Tests/ClientConcepts/Connection/ModifyingDefaultConnection.doc.cs
index fa9c61cbb97..881b0c48e6a 100644
--- a/src/Tests/Tests/ClientConcepts/Connection/ModifyingDefaultConnection.doc.cs
+++ b/src/Tests/Tests/ClientConcepts/Connection/ModifyingDefaultConnection.doc.cs
@@ -11,6 +11,10 @@
 using Tests.Core.Extensions;
 using Tests.Domain;
 using Tests.Framework;
+#if DOTNETCORE
+using System.Net.Http;
+using System.Net.Http.Headers;
+#endif
 
 namespace Tests.ClientConcepts.Connection
 {
@@ -117,6 +121,7 @@ public void InMemoryConnectionOverloadedCtor()
 		* By deriving from `HttpConnection`, it is possible to change the behaviour of the connection. The following
 		* provides some examples
 		*
+		*
 		* [[servicepoint-behaviour]]
 		* ===== ServicePoint behaviour
 		*
@@ -180,5 +185,30 @@ public void UseX509CertificateHttpConnection()
 		 * See <<working-with-certificates, Working with certificates>> for further details.
 		 */
 #endif
+#if DOTNETCORE
+		/*
+		* [[kerberos-authentication]]
+		* ===== Kerberos Authentication
+		*
+		* For a lot of use cases subclassing HttpConnection is a great way to customize the http connection for your needs.
+		* E.g if you want to authenticate with Kerberos, creating a custom HttpConnection as followed allows you to set the right HTTP headers.
+		*
+		*
+		* TIP use something like https://www.nuget.org/packages/Kerberos.NET/ to fill in the actual blanks of this implementation
+		*/
+		public class KerberosConnection : HttpConnection
+		{
+			protected override HttpRequestMessage CreateRequestMessage(RequestData requestData)
+			{
+				var message = base.CreateRequestMessage(requestData);
+				var header = string.Empty;
+				message.Headers.Authorization = new AuthenticationHeaderValue("Negotiate", header);
+				return message;
+			}
+		}
+#endif
+
+
+
 	}
 }