fix typo in MySQL troubleshooting guide (#805)

Author: Solomon-12

docs/Troubleshooting/MySqlIssue.md

@@ -13,7 +13,7 @@ always available, it leads to a rapid increase in MySQL disk consumption.
 This growth is primarily caused by the large size of the binary logs generated
 after each data collection cycle.
 
-### Why dose DevLake choose to delete the existing data and then insert new data?
+### Why does DevLake choose to delete the existing data and then insert new data?
 
 Because we want to ensure that the latest data is 
 always available. If we don't delete the existing data, some old data which has been deleted 

versioned_docs/version-v0.17/Troubleshooting/MySqlSizeIssue.md

@@ -13,7 +13,7 @@ always available, it leads to a rapid increase in MySQL disk consumption.
 This growth is primarily caused by the large size of the binary logs generated
 after each data collection cycle.
 
-### Why dose DevLake choose to delete the existing data and then insert new data?
+### Why does DevLake choose to delete the existing data and then insert new data?
 
 Because we want to ensure that the latest data is 
 always available. If we don't delete the existing data, some old data which has been deleted 

versioned_docs/version-v0.18/Troubleshooting/MySqlSizeIssue.md

@@ -13,7 +13,7 @@ always available, it leads to a rapid increase in MySQL disk consumption.
 This growth is primarily caused by the large size of the binary logs generated
 after each data collection cycle.
 
-### Why dose DevLake choose to delete the existing data and then insert new data?
+### Why does DevLake choose to delete the existing data and then insert new data?
 
 Because we want to ensure that the latest data is 
 always available. If we don't delete the existing data, some old data which has been deleted 

versioned_docs/version-v0.19/Troubleshooting/MySqlSizeIssue.md

@@ -13,7 +13,7 @@ always available, it leads to a rapid increase in MySQL disk consumption.
 This growth is primarily caused by the large size of the binary logs generated
 after each data collection cycle.
 
-### Why dose DevLake choose to delete the existing data and then insert new data?
+### Why does DevLake choose to delete the existing data and then insert new data?
 
 Because we want to ensure that the latest data is 
 always available. If we don't delete the existing data, some old data which has been deleted 

versioned_docs/version-v0.20/Troubleshooting/MySqlIssue.md

@@ -13,7 +13,7 @@ always available, it leads to a rapid increase in MySQL disk consumption.
 This growth is primarily caused by the large size of the binary logs generated
 after each data collection cycle.
 
-### Why dose DevLake choose to delete the existing data and then insert new data?
+### Why does DevLake choose to delete the existing data and then insert new data?
 
 Because we want to ensure that the latest data is 
 always available. If we don't delete the existing data, some old data which has been deleted 

versioned_docs/version-v0.21/Troubleshooting/MySqlIssue.md

@@ -13,7 +13,7 @@ always available, it leads to a rapid increase in MySQL disk consumption.
 This growth is primarily caused by the large size of the binary logs generated
 after each data collection cycle.
 
-### Why dose DevLake choose to delete the existing data and then insert new data?
+### Why does DevLake choose to delete the existing data and then insert new data?
 
 Because we want to ensure that the latest data is 
 always available. If we don't delete the existing data, some old data which has been deleted 

versioned_docs/version-v1.0/Troubleshooting/MySqlIssue.md

@@ -13,7 +13,7 @@ always available, it leads to a rapid increase in MySQL disk consumption.
 This growth is primarily caused by the large size of the binary logs generated
 after each data collection cycle.
 
-### Why dose DevLake choose to delete the existing data and then insert new data?
+### Why does DevLake choose to delete the existing data and then insert new data?
 
 Because we want to ensure that the latest data is 
 always available. If we don't delete the existing data, some old data which has been deleted