Docs: edit lightweight DELETE docs based on feedback

docs/en/sql-reference/statements/delete.md

@@ -4,20 +4,16 @@ sidebar_position: 36
 sidebar_label: DELETE
 description: Lightweight deletes simplify the process of deleting data from the database.
 keywords: [delete]
-title: DELETE Statement
+title: The Lightweight DELETE Statement
 ---
 
-The `DELETE` statement removes rows from the table `[db.]table` that match the expression `expr`.
+The lightweight `DELETE` statement removes rows from the table `[db.]table` that match the expression `expr`. It is only available for the *MergeTree table engine family.
 
 ``` sql
 DELETE FROM [db.]table [ON CLUSTER cluster] WHERE expr;
 ```
 
-Deleted rows are internally marked as deleted immediately and will be automatically filtered out of all subsequent queries. Cleanup of data happens asynchronously in the background until the next merge. As a result, it is possible that for an unspecified period, data is not actually deleted from storage and is only marked as deleted.
-
-The `DELETE` statement is only available for the *MergeTree table engine family.
-
-**Do not use the DELETE statement frequently as it can negatively affect ClickHouse performance.**
+It is called "lightweight `DELETE`" to contrast it to the [ALTER table DELETE](/en/sql-reference/statements/alter/delete) command, which is a heavyweight process.
 
 ## Examples
 
@@ -26,18 +22,35 @@ The `DELETE` statement is only available for the *MergeTree table engine family.
 DELETE FROM hits WHERE Title LIKE '%hello%';
 ```
 
-## Handling large `DELETE`s
+## Lightweight `DELETE` does not delete data from storage immediately
+
+With lightweight `DELETE`, deleted rows are internally marked as deleted immediately and will be automatically filtered out of all subsequent queries. However, cleanup of data happens during the next merge. As a result, it is possible that for an unspecified period, data is not actually deleted from storage and is only marked as deleted.
+
+If you need to guarantee that your data is deleted from storage in a predictable time, consider using the [ALTER table DELETE](/en/sql-reference/statements/alter/delete) command. Note that deleting data using `ALTER table DELETE` may consume significant resources as it recreates all affected parts.
+
+## Deleting large amounts of data
 
 Large deletes can negatively affect ClickHouse performance. If you are attempting to delete all rows from a table, consider using the [`TRUNCATE TABLE`](/en/sql-reference/statements/truncate) command.
 
 If you anticipate frequent deletes, consider using a [custom partitioning key](/en/engines/table-engines/mergetree-family/custom-partitioning-key). You can then use the [`ALTER TABLE...DROP PARTITION`](/en/sql-reference/statements/alter/partition#drop-partitionpart) command to quickly drop all rows associated with that partition.
 
-## Limitations of `DELETE`
+## Limitations of lightweight `DELETE`
 
-### `DELETE`s do not work with projections
+### Lightweight `DELETE`s do not work with projections
 
 Currently, `DELETE` does not work for tables with projections. This is because rows in a projection may be affected by a `DELETE` operation and may require the projection to be rebuilt, negatively affecting `DELETE` performance.
 
+## Performance considerations when using lightweight `DELETE`
+
+**Deleting large volumes of data with the lightweight `DELETE` statement can negatively affect SELECT query performance.**
+
+The following can also negatively impact lightweight `DELETE` performance:
+
+- A heavy `WHERE` condition in a `DELETE` query.
+- If the mutations queue is filled with many other mutations, this can possibly lead to performance issues as all mutations on a table are executed sequentially.
+- The affected table having a very large number of data parts.
+- Having a lot of data in compact parts. In a Compact part, all columns are stored in one file.
+
 ## Delete permissions
 
 `DELETE` requires the `ALTER DELETE` privilege. To enable `DELETE` statements on a specific table for a given user, run the following command:
@@ -46,13 +59,13 @@ Currently, `DELETE` does not work for tables with projections. This is because r
 GRANT ALTER DELETE ON db.table to username;
 ```
 
-## How DELETEs work internally in ClickHouse
+## How lightweight DELETEs work internally in ClickHouse
 
 1. A "mask" is applied to affected rows
 
-When a `DELETE FROM table ...` query is executed, ClickHouse saves a mask where each row is marked as either “existing” or as “deleted”. Those “deleted” rows are omitted for subsequent queries. However, rows are actually only removed later by subsequent merges. Writing this mask is much more lightweight than what is done by an `ALTER table DELETE ...` query.
+When a `DELETE FROM table ...` query is executed, ClickHouse saves a mask where each row is marked as either “existing” or as “deleted”. Those “deleted” rows are omitted for subsequent queries. However, rows are actually only removed later by subsequent merges. Writing this mask is much more lightweight than what is done by an `ALTER table DELETE` query.
 
-The mask is implemented as a hidden `_row_exists` system column that stores `True` for all visible rows and `False` for deleted ones. This column is only present in a part if some rows in this part were deleted. This column does not exist when a part has all values equal to `True`.
+The mask is implemented as a hidden `_row_exists` system column that stores `True` for all visible rows and `False` for deleted ones. This column is only present in a part if some rows in the part were deleted. This column does not exist when a part has all values equal to `True`.
 
 2. `SELECT` queries are transformed to include the mask
 
@@ -70,16 +83,9 @@ Internally, this mutation is executed in two steps:
 
 1. A `SELECT count() FROM table WHERE condition` command is executed for each individual part to determine if the part is affected.
 
-2. Based on the commands above, affected parts are then mutated, and hardlinks are created for unaffected parts. In the case of wide parts, the `_row_exists` column for each row is updated and all other columns' files are hardlinked. For compact parts, all columns are re-written because they all are stored together in one file.
+2. Based on the commands above, affected parts are then mutated, and hardlinks are created for unaffected parts. In the case of wide parts, the `_row_exists` column for each row is updated and all other columns' files are hardlinked. For compact parts, all columns are re-written because they are all stored together in one file.
 
-From the steps above, we can see that lightweight deletes using the masking technique improves performance over traditional `ALTER DELETE` commands because `ALTER DELETE` reads and re-writes all the columns' files for affected parts.
-
-The following can negatively impact `DELETE` performance:
-
-- A heavy `WHERE` condition in `DELETE` query
-- If the mutations queue is filled with other mutations, this can possibly lead to performance issues as all mutations on a table are executed sequentially
-- The affected table having a very large number of data parts
-- Having a lot of data in compact parts. In a Compact part, all columns are stored in one file
+From the steps above, we can see that lightweight deletes using the masking technique improves performance over traditional `ALTER table DELETE` commands because `ALTER table DELETE` reads and re-writes all the columns' files for affected parts.
 
 ## Related content