diff --git a/core/modules/system/core.api.php b/core/modules/system/core.api.php
index 1a812eb..778cdb3 100644
--- a/core/modules/system/core.api.php
+++ b/core/modules/system/core.api.php
@@ -473,18 +473,17 @@
  * @section tags Cache Tags
  *
  * The fourth argument of the set() method can be used to specify cache tags,
- * which are used to identify which data is included in each cache item.
- * A cache item can have multiple cache tags (an array of cache tags), and
- * each cache tag is a string. The convention is to generate cache tags of the
- * form [prefix]:[suffix]. Usually, you'll want to associate the cache tags of
+ * which are used to identify which data is included in each cache item. A cache
+ * item can have multiple cache tags (an array of cache tags), and each cache
+ * tag is a string. The convention is to generate cache tags of the form
+ * [prefix]:[suffix]. Usually, you'll want to associate the cache tags of
  * entities, or entity listings. You won't have to manually construct cache tags
  * for them — just get their cache tags via
  * \Drupal\Core\Entity\EntityInterface::getCacheTags() and
  * \Drupal\Core\Entity\EntityTypeInterface::getListCacheTags().
- * Data that has been tagged can be invalidated as a group: no matter
- * the Cache ID (cid) of the cache item, no matter in which cache bin a cache
- * item lives; as long as it is tagged with a certain cache tag, it will be
- * invalidated.
+ * Data that has been tagged can be invalidated as a group: no matter the Cache
+ * ID (cid) of the cache item, no matter in which cache bin a cache item lives;
+ * as long as it is tagged with a certain cache tag, it will be invalidated.
  *
  * Because of that, cache tags are a solution to the cache invalidation problem:
  * - For caching to be effective, each cache item must only be invalidated when