fix

apache · Jun 22, 2024 · 5441583 · 5441583
1 parent 367a0aa
commit 5441583
Show file tree

Hide file tree

Showing 4 changed files with 9 additions and 9 deletions.
diff --git a/i18n/en/docusaurus-plugin-content-blog/seata-at-tcc-saga.md b/i18n/en/docusaurus-plugin-content-blog/seata-at-tcc-saga.md
@@ -43,7 +43,7 @@ After the business system is split according to services, a complete business of
 <a name="3oIxE"></a>
 ## II. Theoretical foundation of distributed transaction
 
-<a name="akRiW"></a
+<a name="akRiW"></a>
 ### 2.1 Two-stage commit protocols
 
 ! [16_16_18__08_13_2019.jpg](/img/saga/sofameetup3_img/4.jpeg)
@@ -72,7 +72,7 @@ Saga theory is from the paper Sagas published by Hector & Kenneth in 1987.<br
 <a name="fZPaN"></a>
 ## III. Seata and its three patterns explained in detail
 
-<a name="IgVM7"></a
+<a name="IgVM7"></a>
 ### 3.1 Distributed transaction Seata introduction
 
 Seata (Simple Extensible Autonomous Transaction Architecture) is a distributed transaction solution jointly open-sourced by Ant Financial Services and Alibaba in January 2019.Seata has been open-sourced for about half a year, and currently has more than 11,000 stars. Seata has been open source for about half a year, and now has more than 11,000 stars and a very active community. We warmly welcome you to participate in the Seata community construction, together will Seata become the open source distributed transaction benchmark product.
@@ -132,7 +132,7 @@ If the second phase is a rollback, Seata needs to rollback the "business SQL" th
 
 AT mode one phase, two phase commit and rollback are automatically generated by Seata framework, user only need to write "business SQL", then can easily access distributed transaction, AT mode is a kind of distributed transaction solution without any intrusion to business.
 
-<a name="FnD1S"></a
+<a name="FnD1S"></a>
 #### 2.3.2 TCC Mode
 
 In March 2019, Seata open-sourced the TCC pattern, which is contributed by Ant Gold. the TCC pattern requires users to implement Try, Confirm and Cancel operations according to their business scenarios; the transaction initiator executes the Try method in the first stage, the Confirm method in the second-stage commit, and the Cancel method in the second-stage rollback.

diff --git a/i18n/en/docusaurus-plugin-content-blog/seata-client-start-analysis-01.md b/i18n/en/docusaurus-plugin-content-blog/seata-client-start-analysis-01.md
@@ -42,7 +42,7 @@ After the business system is split according to services, a complete business of
 <a name="3oIxE"></a>
 ## II. Theoretical foundation of distributed transaction
 
-<a name="akRiW"></a
+<a name="akRiW"></a>
 ### 2.1 Two-stage commit protocols
 
 ! [16_16_18__08_13_2019.jpg](/img/saga/sofameetup3_img/4.jpeg)
@@ -71,7 +71,7 @@ Saga theory is from the paper Sagas published by Hector & Kenneth in 1987.<br
 <a name="fZPaN"></a>
 ## III. Seata and its three patterns explained in detail
 
-<a name="IgVM7"></a
+<a name="IgVM7"></a>
 ### 3.1 Distributed transaction Seata introduction
 
 Seata (Simple Extensible Autonomous Transaction Architecture) is a distributed transaction solution jointly open-sourced by Ant Financial Services and Alibaba in January 2019.Seata has been open-sourced for about half a year, and currently has more than 11,000 stars. Seata has been open source for about half a year, and now has more than 11,000 stars and a very active community. We warmly welcome you to participate in the Seata community construction, together will Seata become the open source distributed transaction benchmark product.
@@ -131,7 +131,7 @@ If the second phase is a rollback, Seata needs to rollback the "business SQL" th
 
 AT mode one phase, two phase commit and rollback are automatically generated by Seata framework, user only need to write "business SQL", then can easily access distributed transaction, AT mode is a kind of distributed transaction solution without any intrusion to business.
 
-<a name="FnD1S"></a
+<a name="FnD1S"></a>
 #### 2.3.2 TCC Mode
 
 In March 2019, Seata open-sourced the TCC pattern, which is contributed by Ant Gold. the TCC pattern requires users to implement Try, Confirm and Cancel operations according to their business scenarios; the transaction initiator executes the Try method in the first stage, the Confirm method in the second-stage commit, and the Cancel method in the second-stage rollback.

diff --git a/i18n/en/docusaurus-plugin-content-blog/seata-client-start-analysis-02.md b/i18n/en/docusaurus-plugin-content-blog/seata-client-start-analysis-02.md
@@ -11,8 +11,8 @@ tags:
 
 > "Just getting started with Seata and don't know enough about its modules? <br />
 Want to dive into the Seata source code, but haven't done so yet? <br />
-Want to find out what your application is doing "on the sly" during startup after integrating Seata? <br
-Want to learn the design concepts and best practices of Seata as a great open source framework? <br
+Want to find out what your application is doing "on the sly" during startup after integrating Seata? <br />
+Want to learn the design concepts and best practices of Seata as a great open source framework? <br />
 If any of the above apply to you, then today's article is for you!
 
 ## Preface

diff --git a/i18n/en/docusaurus-plugin-content-blog/seata-dsproxy-deadlock.md b/i18n/en/docusaurus-plugin-content-blog/seata-dsproxy-deadlock.md
@@ -286,7 +286,7 @@ The problem can be solved in two ways:
  ```
 
 I wanted to change the `CollectionUtils#computeIfAbsent` method directly, and the feedback from the group was that this might cause the data source to be created multiple times, which is indeed a problem: as follows
-``java
+```java
 public static <K, V> V computeIfAbsent(Map<K, V> map, K key, Function<? super K, ? extends V> mappingFunction) {
 V value = map.get(key);
 if (value ! = null) {