From 076f0769618c3fee622ccd53568a5fccd521de63 Mon Sep 17 00:00:00 2001
From: achatterjee-grafana
 <70489351+achatterjee-grafana@users.noreply.github.com>
Date: Mon, 10 May 2021 13:55:00 -0400
Subject: [PATCH] Removed content as per MarcusE's suggestion in
 https://github.com/grafana/grafana/issues/33822. (#33870)

---
 docs/sources/administration/set-up-for-high-availability.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/administration/set-up-for-high-availability.md b/docs/sources/administration/set-up-for-high-availability.md
index e49cfed4d2e..7a4a2636aa6 100644
--- a/docs/sources/administration/set-up-for-high-availability.md
+++ b/docs/sources/administration/set-up-for-high-availability.md
@@ -26,4 +26,4 @@ Currently alerting supports a limited form of high availability. [Alert notifica
 
 ## User sessions
 
-Grafana uses auth token strategy with database by default. This means that a load balancer can send a user to any Grafana server without having to log in on each server. If you want to offload the login session data from the database, then you can configure [remote_cache]({{< relref "../administration/configuration.md" >}}#remote-cache).
+Grafana uses auth token strategy with database by default. This means that a load balancer can send a user to any Grafana server without having to log in on each server.