deploy: e9c4077

pingcap · Sep 4, 2024 · 59bc986 · 59bc986
1 parent 249ec5f
commit 59bc986
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/print.html b/print.html
@@ -2029,7 +2029,7 @@ <h2 id="a-short-introduction-to-tidbs-ddl"><a class="header" href="#a-short-intr
         // StatePublic means this schema element is ok for all write and read operations.
         StatePublic
 </code></pre>
-<p>Note: this is a very different implementation from MySQL, which uses Meta Data Locks (MDL) for keeping a single version of the MySQL instance schemas at a time. This results in MySQL replicas can have different version of the schemas, due to lag in asyncronous replication. TiDB has always a consistent view of all schemas in the cluster.</p>
+<p>Note: this is a very different implementation from MySQL, which uses Meta Data Locks (MDL) for keeping a single version of the MySQL instance schemas at a time. This results in MySQL replicas can have different version of the schemas, due to lag in asynchronous replication. TiDB has always a consistent view of all schemas in the cluster.</p>
 <h2 id="implementation"><a class="header" href="#implementation">Implementation</a></h2>
 <p>All DDL jobs goes through two cluster wide DDL Queues:</p>
 <ul>

diff --git a/searchindex.js b/searchindex.js
diff --git a/searchindex.json b/searchindex.json
diff --git a/understand-tidb/ddl.html b/understand-tidb/ddl.html
@@ -195,7 +195,7 @@ <h2 id="a-short-introduction-to-tidbs-ddl"><a class="header" href="#a-short-intr
         // StatePublic means this schema element is ok for all write and read operations.
         StatePublic
 </code></pre>
-<p>Note: this is a very different implementation from MySQL, which uses Meta Data Locks (MDL) for keeping a single version of the MySQL instance schemas at a time. This results in MySQL replicas can have different version of the schemas, due to lag in asyncronous replication. TiDB has always a consistent view of all schemas in the cluster.</p>
+<p>Note: this is a very different implementation from MySQL, which uses Meta Data Locks (MDL) for keeping a single version of the MySQL instance schemas at a time. This results in MySQL replicas can have different version of the schemas, due to lag in asynchronous replication. TiDB has always a consistent view of all schemas in the cluster.</p>
 <h2 id="implementation"><a class="header" href="#implementation">Implementation</a></h2>
 <p>All DDL jobs goes through two cluster wide DDL Queues:</p>
 <ul>