[skywalking] branch metric-cache updated: Fix words

[wu...@apache.org]

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

wusheng pushed a commit to branch metric-cache
in repository https://gitbox.apache.org/repos/asf/skywalking.git


The following commit(s) were added to refs/heads/metric-cache by this push:
     new 0f139caf74 Fix words
0f139caf74 is described below

commit 0f139caf74348a4cb282d2fc99fe6a5cae46de6c
Author: Wu Sheng <wu...@foxmail.com>
AuthorDate: Thu Nov 24 15:39:20 2022 +0800

    Fix words
---
 docs/en/changes/changes.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/en/changes/changes.md b/docs/en/changes/changes.md
index e4f4e855c9..e6ba8c629b 100644
--- a/docs/en/changes/changes.md
+++ b/docs/en/changes/changes.md
@@ -119,11 +119,11 @@
 * Support dynamic config the sampling strategy in network profiling.
 * Zipkin module support BanyanDB storage.
 * Zipkin traces query API, sort the result set by start time by default.
-* Enhance cache mechanism in the metric persistent process.
-  * This cache only worked when the metric is accessible(readable) from the database. Once the insert execution delayed
-    due to the scale, the cache would lose efficacy. It only works for the last time update per minute, considering our
+* Enhance the cache mechanism in the metric persistent process.
+  * This cache only worked when the metric is accessible(readable) from the database. Once the insert execution is delayed
+    due to the scale, the cache loses efficacy. It only works for the last time update per minute, considering our
     25s period.
-  * Fix ID conflicts for all JDBC storage implementation. Due to insert delay, the JDBC storage implementation would
+  * Fix ID conflicts for all JDBC storage implementations. Due to the insert delay, the JDBC storage implementation would
     still generate another new insert statement.
 
 #### UI