This is an automated email from the ASF dual-hosted git repository.
klesh pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git
The following commit(s) were added to refs/heads/main by this push:
new f706b10321b fix typo in MySQL troubleshooting guide (#805)
f706b10321b is described below
commit f706b10321bc02612c390a88a3865f9ff5052fda
Author: Solomon Wong <47252236+solomon...@users.noreply.github.com>
AuthorDate: Wed Jul 30 11:14:08 2025 +0800
fix typo in MySQL troubleshooting guide (#805)
---
docs/Troubleshooting/MySqlIssue.md | 2 +-
versioned_docs/version-v0.17/Troubleshooting/MySqlSizeIssue.md | 2 +-
versioned_docs/version-v0.18/Troubleshooting/MySqlSizeIssue.md | 2 +-
versioned_docs/version-v0.19/Troubleshooting/MySqlSizeIssue.md | 2 +-
versioned_docs/version-v0.20/Troubleshooting/MySqlIssue.md | 2 +-
versioned_docs/version-v0.21/Troubleshooting/MySqlIssue.md | 2 +-
versioned_docs/version-v1.0/Troubleshooting/MySqlIssue.md | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)
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
