Skip to content

docs: correct typo in Mysql Troubleshooting guide #805

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
klesh merged 1 commit into from
Jul 30, 2025
Merged

docs: correct typo in Mysql Troubleshooting guide #805

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/Troubleshooting/MySqlIssue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-v0.17/Troubleshooting/MySqlSizeIssue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-v0.18/Troubleshooting/MySqlSizeIssue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-v0.19/Troubleshooting/MySqlSizeIssue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-v0.20/Troubleshooting/MySqlIssue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-v0.21/Troubleshooting/MySqlIssue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-v1.0/Troubleshooting/MySqlIssue.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down