[shardingsphere] branch master updated: Update sharding-cache.en.md (#22474)

[zh...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

zhaojinchao pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git


The following commit(s) were added to refs/heads/master by this push:
     new 05283a549c5 Update sharding-cache.en.md (#22474)
05283a549c5 is described below

commit 05283a549c5f8de42b355f88bf6c1f64a345b5ff
Author: Yacine Si Tayeb <86...@users.noreply.github.com>
AuthorDate: Mon Nov 28 13:46:59 2022 +0800

    Update sharding-cache.en.md (#22474)
---
 .../yaml-config/rules/sharding-cache.en.md               | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding-cache.en.md b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding-cache.en.md
index 32e99faaa7b..a189a31ae29 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding-cache.en.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/rules/sharding-cache.en.md
@@ -5,14 +5,14 @@ weight = 10
 
 ## Background
 
-This feature is **experimental** and needs to be used with data sharding rule.
-The cache for sharding route will put the logical SQL, the actual parameter value of the shard key, and the routing result into the cache, exchange space for time, and reduce the CPU usage of routing logic.
-
-It is recommended to enable only if the following conditions are met:
-- Pure OLTP scenarios
-- The CPU of the machine which deployed the ShardingSphere process has reached the bottleneck
-- Most of the CPUs are used by ShardingSphere routing logic
-- All SQLs are optimized and each SQL execution could be routed to a single data node
+This feature is **experimental** and needs to be used with the data sharding rule.
+The cache for sharding route will put the logical SQL, the parameter value of the shard key, and the routing result into the cache, exchange space for time, and reduce CPU usage of the routing logic.
+
+We recommend enabling it only if the following conditions are met:
+- Pure OLTP scenarios.
+- The CPU of the machine which deployed the ShardingSphere process has reached the bottleneck.
+- Most of the CPUs are used by ShardingSphere routing logic.
+- All SQLs are optimized and each SQL execution could be routed to a single data node.
 
 If the above conditions are not met, the execution delay of SQL may not be significantly improved, and the memory pressure will be increased.