You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by ni...@apache.org on 2019/01/29 03:36:33 UTC

[servicecomb-docs] branch master updated: Update design_zh.md

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

ningjiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git


The following commit(s) were added to refs/heads/master by this push:
     new 741b384  Update design_zh.md
741b384 is described below

commit 741b3846df285117bb99f2e00cbc8f83075155eb
Author: fff <pu...@gmail.com>
AuthorDate: Mon Jan 28 10:50:16 2019 +0800

    Update design_zh.md
    
    修改TCC具体处理流程 ‘各方’ ‘相关各方’理解歧义
---
 saga-reference/zh_CN/design_zh.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/saga-reference/zh_CN/design_zh.md b/saga-reference/zh_CN/design_zh.md
index afbb07e..eb72039 100644
--- a/saga-reference/zh_CN/design_zh.md
+++ b/saga-reference/zh_CN/design_zh.md
@@ -34,7 +34,7 @@ Saga处理场景是要求相关的子事务提供事务处理函数同时也提
 ![Timeout Scenario](static_files/timeout_scenario.png)
 
 ## TCC 具体处理流程
-TCC(try-confirm-cancel)与Saga事务处理方式相比多了一个Try方法。事务调用的发起方来根据事务的执行情况协调各方相关各方进行提交事务或者回滚事务。
+TCC(try-confirm-cancel)与Saga事务处理方式相比多了一个Try方法。事务调用的发起方来根据事务的执行情况协调相关各方进行提交事务或者回滚事务。
 ### 成功场景
 成功场景下, 每个事务都会有开始和对应的结束事件