[dubbo-website] branch master updated: Update serialization-upgrade.md

[albumenj]

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

albumenj pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dubbo-website.git


The following commit(s) were added to refs/heads/master by this push:
     new 4689a81ec53 Update serialization-upgrade.md
4689a81ec53 is described below

commit 4689a81ec53d1901b303bee8f792e7d807eb9b3a
Author: Albumen Kevin <jhq0...@gmail.com>
AuthorDate: Sat Oct 8 11:23:54 2022 +0800

    Update serialization-upgrade.md
---
 .../java-sdk/upgrades-and-compatibility/serialization-upgrade.md        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/content/zh/docs3-v2/java-sdk/upgrades-and-compatibility/serialization-upgrade.md
 
b/content/zh/docs3-v2/java-sdk/upgrades-and-compatibility/serialization-upgrade.md
index e383d05ee81..3c0091d755e 100644
--- 
a/content/zh/docs3-v2/java-sdk/upgrades-and-compatibility/serialization-upgrade.md
+++ 
b/content/zh/docs3-v2/java-sdk/upgrades-and-compatibility/serialization-upgrade.md
@@ -25,5 +25,5 @@ dubbo.provider.serialization=hessian2
 
 **实现原理**
 
-dubbo 客户端序列化协议是根据服务端的注册配置来选择的（即服务端的`serialization`配置）。在请求阶段 dubbo 
会把客户端的序列化协议组装到请求头上，服务端在进行反序列化时会根据请求头来确定反序列化协议。**所以，如果服务端和客户端的版本不一致就可能会出现客户端序列化不了的情况。**
 为了解决这个情况，3.1.1 
在客户端序列化的时候会优先使用`prefer-serialization`配置的协议，如果不支持`prefer-serialization`相关的协议，才会使用`serialization`配置的协议。（可以把`serialization`理解为一个兜底的配置）
+dubbo 客户端序列化协议是根据服务端的注册配置来选择的（即服务端的`serialization`配置）。在请求阶段 dubbo 
会把客户端的序列化协议组装到请求头上，服务端在进行反序列化时会根据请求头来确定反序列化协议。**所以，如果服务端和客户端的版本不一致就可能会出现客户端序列化不了的情况。**
 为了解决这个情况，3.2.0 
在客户端序列化的时候会优先使用`prefer-serialization`配置的协议，如果不支持`prefer-serialization`相关的协议，才会使用`serialization`配置的协议。（可以把`serialization`理解为一个兜底的配置）