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

@@ -23,7 +23,7 @@ Some common database operations include mass writes to the database, including t
 
 These operations can easily incur replication lag. However, these operations are typically not time-limited. It is possible to rate-limit them to reduce database load.
 
-This is where a throttler gets in. A throttler can tell "replication lag is low, cluster is healthy, go ahead and do some work" or it may say "replication lag is high, please hold your next operation".
+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.