diff --git a/core/lib/Drupal/Core/Lock/LockBackendInterface.php b/core/lib/Drupal/Core/Lock/LockBackendInterface.php
index c84e42d..3dd2eae 100644
--- a/core/lib/Drupal/Core/Lock/LockBackendInterface.php
+++ b/core/lib/Drupal/Core/Lock/LockBackendInterface.php
@@ -13,12 +13,11 @@
  * Functions to coordinate long-running operations across requests.
  *
  * In most environments, multiple Drupal page requests (a.k.a. threads or
- * processes) will execute in parallel. This leads to potential conflicts or
- * race conditions when two requests execute the same code at the same time. A
- * common example of this is a rebuild like menu_router_rebuild() where we
- * invoke many hook implementations to get and process data from all active
- * modules, and then delete the current data in the database to insert the new
- * afterwards.
+ * processes) will execute in parallel. This leads to potential conflicts,
+ * race conditions or unnecessary resource usage, when two requests execute the
+ * same code at the same time. A common example of this is a rebuild like
+ * RouteBuilder::rebuild() where we invoke many hook implementations to get and
+ * process data from all active modules.
  *
  * This is a cooperative, advisory lock system. Any long-running operation
  * that could potentially be attempted in parallel by multiple requests should