diff --git a/docs/Troubleshooting/MySqlIssue.md b/docs/Troubleshooting/MySqlIssue.md index c05dadf13cc..f30ea28ef41 100644 --- a/docs/Troubleshooting/MySqlIssue.md +++ b/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 diff --git a/versioned_docs/version-v0.17/Troubleshooting/MySqlSizeIssue.md b/versioned_docs/version-v0.17/Troubleshooting/MySqlSizeIssue.md index 3226b7dc0f1..c5081f06a3e 100644 --- a/versioned_docs/version-v0.17/Troubleshooting/MySqlSizeIssue.md +++ b/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 diff --git a/versioned_docs/version-v0.18/Troubleshooting/MySqlSizeIssue.md b/versioned_docs/version-v0.18/Troubleshooting/MySqlSizeIssue.md index 3226b7dc0f1..c5081f06a3e 100644 --- a/versioned_docs/version-v0.18/Troubleshooting/MySqlSizeIssue.md +++ b/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 diff --git a/versioned_docs/version-v0.19/Troubleshooting/MySqlSizeIssue.md b/versioned_docs/version-v0.19/Troubleshooting/MySqlSizeIssue.md index 3226b7dc0f1..c5081f06a3e 100644 --- a/versioned_docs/version-v0.19/Troubleshooting/MySqlSizeIssue.md +++ b/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 diff --git a/versioned_docs/version-v0.20/Troubleshooting/MySqlIssue.md b/versioned_docs/version-v0.20/Troubleshooting/MySqlIssue.md index c05dadf13cc..f30ea28ef41 100644 --- a/versioned_docs/version-v0.20/Troubleshooting/MySqlIssue.md +++ b/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 diff --git a/versioned_docs/version-v0.21/Troubleshooting/MySqlIssue.md b/versioned_docs/version-v0.21/Troubleshooting/MySqlIssue.md index c05dadf13cc..f30ea28ef41 100644 --- a/versioned_docs/version-v0.21/Troubleshooting/MySqlIssue.md +++ b/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 diff --git a/versioned_docs/version-v1.0/Troubleshooting/MySqlIssue.md b/versioned_docs/version-v1.0/Troubleshooting/MySqlIssue.md index c05dadf13cc..f30ea28ef41 100644 --- a/versioned_docs/version-v1.0/Troubleshooting/MySqlIssue.md +++ b/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