From c04cce903fd485c862856a8cb6d5b49c804ed854 Mon Sep 17 00:00:00 2001
From: "Grot (@grafanabot)" <43478413+grafanabot@users.noreply.github.com>
Date: Tue, 19 Jul 2022 14:34:15 +0000
Subject: [PATCH] Docs: Update query caching support (#50706) (#52461)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* Docs: Update query caching support

* Update query-caching.md

(cherry picked from commit 2b7fe7251cbf3a318e8ba37925f16fb5b2c65607)

Co-authored-by: Agnès Toulet <35176601+AgnesToulet@users.noreply.github.com>
---
 docs/sources/enterprise/query-caching.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/enterprise/query-caching.md b/docs/sources/enterprise/query-caching.md
index a781eff7be1..8f9a444cb87 100644
--- a/docs/sources/enterprise/query-caching.md
+++ b/docs/sources/enterprise/query-caching.md
@@ -15,7 +15,7 @@ weight: 300
 
 When query caching is enabled, Grafana temporarily stores the results of data source queries. When you or another user submit the exact same query again, the results will come back from the cache instead of from the data source (like Splunk or ServiceNow) itself.
 
-Query caching works for all backend data sources, and queries sent through the data source proxy. You can enable the cache globally and configure the cache duration (also called Time to Live, or TTL).
+Query caching works for all backend data sources. You can enable the cache globally and configure the cache duration (also called Time to Live, or TTL).
 
 The following cache backends are available: in-memory, Redis, and Memcached.