Update content/en/docs/reference/features/tablet-throttler.md

Co-authored-by: Byron Landry <byronlandry@planetscale.com>

content/en/docs/reference/features/tablet-throttler.md

@@ -25,7 +25,7 @@ These operations can easily incur replication lag. However, these operations are
 
 This is where a throttler becomes useful. A throttler can detect when replication lag is low, a cluster is healthy, and operations can proceed. It can also detect when replication lag is high and advise applications to hold the next operation.
 
-Applications are expected to break down their tasks into small sub-tasks (e.g. instead of deleting `1,000,000` rows, only delete `50` at a time), and check in with the throttler in-between.
+Applications are expected to break down their tasks into small sub-tasks. For example, instead of deleting `1,000,000` rows, an application should only delete `50` at a time. Between these sub-tasks, the application should check in with the throttler.
 
 The throttler is only intended for use with operations such as the above mass write cases. It should not be used for ongoing, normal OLTP queries.