Update release note for v1.13

Signed-off-by: Kevin Wang <kevinwzf0126@gmail.com>

1 files changed, 19 insertions, 25 deletions

diff --git a/CHANGELOG/CHANGELOG-1.13.md b/CHANGELOG/CHANGELOG-1.13.md
index 97c9a3993..1607dad96 100644
--- a/CHANGELOG/CHANGELOG-1.13.md
+++ b/CHANGELOG/CHANGELOG-1.13.md
@@ -21,13 +21,13 @@ Download v1.13.0 in the [v1.13.0 release page](https://github.com/kubeedge/kubee
 
 ### Performance Improvement
 
-- Add prometheus monitor server and a metric connected_nodes to cloudHub. This metric tallies the number of connected nodes each cloudhub instance ([#3646](https://github.com/kubeedge/kubeedge/pull/3646))
-- Add pprof for visualization and analysis of profiling data ([#3646](https://github.com/kubeedge/kubeedge/pull/3646))
-- CloudCore configuration is automatically adjusted according to nodeLimit to adapt to the number of nodes of different scales ([#4376](https://github.com/kubeedge/kubeedge/pull/4376))
-- CloudCore memory usage optimization. Through unified generic Informer and reduce unnecessary cache, memory usage is reduced by 40% ([#4375](https://github.com/kubeedge/kubeedge/pull/4375)) ([#4377](https://github.com/kubeedge/kubeedge/pull/4377))
+- **CloudCore memory usage is reduced by 40%**, through unified generic Informer and reduce unnecessary cache. ([#4375](https://github.com/kubeedge/kubeedge/pull/4375)) ([#4377](https://github.com/kubeedge/kubeedge/pull/4377))
 - List-watch dynamicController processing optimization, each watcher has a separate channel and goroutine processing to improve processing efficiency ([#4506](https://github.com/kubeedge/kubeedge/pull/4506))
-- fix 10s delay for edge request when the node is offline ([#4490](https://github.com/kubeedge/kubeedge/pull/4490))
 - Added list-watch synchronization mechanism between cloud and edge and add dynamicController watch gc mechanism ([#4484](https://github.com/kubeedge/kubeedge/pull/4484))
+- Removed 10s hard delay when offline nodes turn online ([#4490](https://github.com/kubeedge/kubeedge/pull/4490))
+- Added prometheus monitor server and a metric connected_nodes to cloudHub. This metric tallies the number of connected nodes each cloudhub instance ([#3646](https://github.com/kubeedge/kubeedge/pull/3646))
+- Added pprof for visualization and analysis of profiling data ([#3646](https://github.com/kubeedge/kubeedge/pull/3646))
+- CloudCore configuration is now automatically adjusted according to nodeLimit to adapt to the number of nodes of different scales ([#4376](https://github.com/kubeedge/kubeedge/pull/4376))
 
 
 ### Security Improvement
@@ -39,12 +39,11 @@ Download v1.13.0 in the [v1.13.0 release page](https://github.com/kubeedge/kubee
 - Remove the token field in the edge node configuration file edgecore.yaml to eliminate the risk of edge information leakage ([#4488](https://github.com/kubeedge/kubeedge/pull/4488))
 
 
-### Upgrade Kubernetes Dependency
+### Upgrade Kubernetes Dependency to v1.23.15
 
-Upgrade the vendered kubernetes version to v1.23.15,users now can use the feature of new version on the cloud and on the edge side.
+Upgrade the vendered kubernetes version to v1.23.15, users are now able to use the feature of new version on the cloud and on the edge side.
 
-Refer to the links for more details.
-([#4509](https://github.com/kubeedge/kubeedge/pull/4509))
+Refer to the link for more details. ([#4509](https://github.com/kubeedge/kubeedge/pull/4509))
 
 
 ### Modbus Mapper based on DMI
@@ -52,40 +51,35 @@ Refer to the links for more details.
 Modbus Device Mapper based on DMI is provided, which is used to access Modbus protocol
 devices and uses DMI to synchronize the management plane messages of devices with edgecore.
 
-Refer to the links for more details.
-([mappers-go#79](https://github.com/kubeedge/mappers-go/pull/79))
+Refer to the link for more details. ([mappers-go#79](https://github.com/kubeedge/mappers-go/pull/79))
 
 
-### Support Setting Concurrent Count for Edge Node Upgrade from Cloud
+### Support Rolling Upgrade for Edge Nodes from Cloud
 
+Users now able to trigger rolling upgrade for edge nodes from cloud, and specify number of concurrent upgrade nodes with `nodeupgradejob.spec.concurrency`. 
+The default Concurrency value is 1, which means upgrade edge nodes one by one.
+Refer to the link for more details. ([#4476](https://github.com/kubeedge/kubeedge/pull/4476))
 
-Support upgrading nodes one by one, but not upgrade them all once a time. Concurrency specifies the max number of edge nodes that can be upgraded at the same time. 
-The default Concurrency value is 1. So that we can upgrade edge nodes one by one.
-Refer to the links for more details.
-([#4476](https://github.com/kubeedge/kubeedge/pull/4476))
-
-### Test Runner
+### Test Runner for conformance test
 
 KubeEdge has provided the runner of the conformance test, which contains the scripts 
 and related files of the conformance test. 
-Follow the [instructions.md](https://github.com/kubeedge/community/pull/130/files#diff-1d40b792672f83aebb7d935e70885b4a3ee0cb612f1b7ce56c96da42676b928bR1) perform a conformance test ([#4411](https://github.com/kubeedge/kubeedge/pull/4411))
+Refer to the link for more details. ([#4411](https://github.com/kubeedge/kubeedge/pull/4411))
 
-### EdgeMesh —— Added configurable field TunnelLimitConfig to edge-tunnel module @jiezhang
+### EdgeMesh —— Added configurable field TunnelLimitConfig to edge-tunnel module
 
 The tunnel stream of the edge-tunnel module is used to manage the data stream state of the tunnel. 
 Users can obtain a stable and configurable tunnel stream to ensure the reliability of user application traffic forwarding.
 
 Users can configure the cache size of tunnel stream according to `TunnelLimitConfig` to support larger application relay traffic.
-Refer to the links for more details.
-([#399](https://github.com/kubeedge/edgemesh/pull/399))
+Refer to the link for more details. ([#399](https://github.com/kubeedge/edgemesh/pull/399))
 
 Cancel the restrictions on the relay to ensure the stability of the user's streaming application or long link application.
-Refer to the links for more details.
-([#400](https://github.com/kubeedge/edgemesh/pull/400))
+Refer to the link for more details. ([#400](https://github.com/kubeedge/edgemesh/pull/400))
 
 
 
 ## Important Steps before Upgrading
 
-- EdgeCore uses `containerd` runtime by default on KubeEdge v1.13. If you want to use `docker` runtime, you
+- EdgeCore now uses `containerd` runtime by default on KubeEdge v1.13. If you want to use `docker` runtime, you
   must set `edged.containerRuntime=docker` and corresponding docker configuration like `DockerEndpoint`, `RemoteRuntimeEndpoint` and `RemoteImageEndpoint` in EdgeCore.