From 236f280688ec83b3b420cd55688a18c1a49197a8 Mon Sep 17 00:00:00 2001
From: Paul Wright <5154224+pwright@users.noreply.github.com>
Date: Thu, 16 Sep 2021 17:06:20 +0100
Subject: [PATCH] remove duplicate cache-timeout docs

---
 docs/user-manual/en/broker-balancers.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/user-manual/en/broker-balancers.md b/docs/user-manual/en/broker-balancers.md
index 30f773d6d4..e588a9e980 100644
--- a/docs/user-manual/en/broker-balancers.md
+++ b/docs/user-manual/en/broker-balancers.md
@@ -102,8 +102,8 @@ A policy is defined by the `policy` element. Let's take a look at a policy examp
 The broker balancer provides a cache with a timeout to improve the stickiness of the target broker selected,
 returning the same target broker for a target key as long as it is present in the cache and is ready.
 So a broker balancer with the cache enabled doesn't strictly follow the configured policy.
-By default, the cache is enabled, and will never timeout. Set `cache-timeout` parameter to 
-a value in seconds for time out, or disable the cache by setting the value to `0`.
+By default, the cache is enabled, and will never timeout. See below
+for more details about setting the `cache-timeout` parameter.
 
 ## Defining broker balancers
 A broker balancer is defined by `broker-balancer` element, it includes the following items: