diff --git a/docs/design/2020-05-11-heap-profile-record.md b/docs/design/2020-05-11-heap-profile-record.md
index 0b5d2710cbc90..dc06b21ee665c 100644
--- a/docs/design/2020-05-11-heap-profile-record.md
+++ b/docs/design/2020-05-11-heap-profile-record.md
@@ -65,7 +65,7 @@ We can find that the `hash` (the key of cache) and the `element`(the value of th
 3. we use [sizeof](https://github.com/templarbit/sizeof) (the result is similar, but lower, not exact) to calculate the size of each key and element is 80byte and 40byte.
 4. As 2.28 MB (120 byte * 20000) is similar to the 2.55MB, we can ensure that the heap profile would reflect the heap usage of `SimpleLRUCache`.
 
-## Compatibility and Mirgration Plan
+## Compatibility and Migration Plan
 
 None
 
diff --git a/docs/design/2020-09-30-index-usage-information.md b/docs/design/2020-09-30-index-usage-information.md
index 0cef46f599aae..2811f49fde1fd 100644
--- a/docs/design/2020-09-30-index-usage-information.md
+++ b/docs/design/2020-09-30-index-usage-information.md
@@ -175,7 +175,7 @@ Write privilege: These tables are read-only. You can use FLUSH SCHEMA_INDEX_USAG
 		- end_monitoring
 - Oracle can set whether to monitor an index.
 
-## Compatibility and Mirgration Plan
+## Compatibility and Migration Plan
 
 MySQL supports `SCHEMA_UNUSED_INDEXES`. We are considering compatibility and also support this view.