From f460b121603886eca1b954ba8d7d0fe3aa7b26b3 Mon Sep 17 00:00:00 2001
From: TomShawn <41534398+TomShawn@users.noreply.github.com>
Date: Thu, 12 Jan 2023 13:40:33 +0800
Subject: [PATCH] update a ddl command (#11935)

---
 placement-rules-in-sql.md                     | 4 ++--
 sql-statements/sql-statement-recover-table.md | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/placement-rules-in-sql.md b/placement-rules-in-sql.md
index a4482bcdd0254..e665c471c123d 100644
--- a/placement-rules-in-sql.md
+++ b/placement-rules-in-sql.md
@@ -15,7 +15,7 @@ The detailed user scenarios are as follows:
 
 - Merge multiple databases of different applications to reduce the cost on database maintenance
 - Increase replica count for important data to improve the application availability and data reliability
-- Store new data into NVMe storage and store old data into SSDs to lower the cost on data archiving and storage 
+- Store new data into NVMe storage and store old data into SSDs to lower the cost on data archiving and storage
 - Schedule the leaders of hotspot data to high-performance TiKV instances
 - Separate cold data to lower-cost storage mediums to improve cost efficiency
 - Support the physical isolation of computing resources between different users, which meets the isolation requirements of different users in a cluster, and the isolation requirements of CPU, I/O, memory, and other resources with different mixed loads
@@ -262,5 +262,5 @@ In dictionary format, constraints also indicate a number of instances that apply
 The following known limitations are as follows:
 
 * Temporary tables do not support placement options.
-* Syntactic sugar rules are permitted for setting `PRIMARY_REGION` and `REGIONS`. In the future, we plan to add varieties for `PRIMARY_RACK`, `PRIMARY_ZONE`, and `PRIMARY_HOST`. See [issue #18030](https://github.com/pingcap/tidb/issues/18030). 
+* Syntactic sugar rules are permitted for setting `PRIMARY_REGION` and `REGIONS`. In the future, we plan to add varieties for `PRIMARY_RACK`, `PRIMARY_ZONE`, and `PRIMARY_HOST`. See [issue #18030](https://github.com/pingcap/tidb/issues/18030).
 * Placement rules only ensure that data at rest resides on the correct TiKV store. The rules do not guarantee that data in transit (via either user queries or internal operations) only occurs in a specific region.
diff --git a/sql-statements/sql-statement-recover-table.md b/sql-statements/sql-statement-recover-table.md
index 2f18b6fa739d6..87f12aa90e753 100644
--- a/sql-statements/sql-statement-recover-table.md
+++ b/sql-statements/sql-statement-recover-table.md
@@ -19,7 +19,7 @@ RECOVER TABLE table_name;
 {{< copyable "sql" >}}
 
 ```sql
-RECOVER TABLE BY JOB ddl_job_id;
+RECOVER TABLE BY JOB JOB_ID;
 ```
 
 ## Synopsis