symfony
diff --git a/‎src/Symfony/Component/Cache/Adapter/RedisTagAwareAdapter.php
Copy file name to clipboardExpand all lines: src/Symfony/Component/Cache/Adapter/RedisTagAwareAdapter.php
+3-3Lines changed: 3 additions & 3 deletions b/‎src/Symfony/Component/Cache/Adapter/RedisTagAwareAdapter.php
Copy file name to clipboardExpand all lines: src/Symfony/Component/Cache/Adapter/RedisTagAwareAdapter.php
+3-3Lines changed: 3 additions & 3 deletions
@@ -18,21 +18,21 @@
 use Symfony\Component\Cache\Traits\RedisTrait;
 
 /**
- * Stores tag id <> cache id relationship as a Redis Set, lookup on invalidation using sPOP.
+ * Stores tag id <> cache id relationship as a Redis Set, lookup on invalidation using RENAME+SMEMBERS.
  *
  * Set (tag relation info) is stored without expiry (non-volatile), while cache always gets an expiry (volatile) even
  * if not set by caller. Thus if you configure redis with the right eviction policy you can be safe this tag <> cache
  * relationship survives eviction (cache cleanup when Redis runs out of memory).
  *
  * Requirements:
  *  - Client: PHP Redis or Predis
- *            Due to lack of RENAME support it is not recommended to use PredisCluster, instead use RedisCluster.
+ *            Note: Due to lack of RENAME support it is not recommended to use Cluster on Predis, instead use phpredis.
  *  - Server: Redis 2.8+
  *            Configured with any `volatile-*` eviction policy, OR `noeviction` if it will NEVER fill up memory
  *
  * Design limitations:
  *  - Max 4 billion cache keys per cache tag as limited by Redis Set datatype.
- *    E.g. If you use a "all" items tag for expiry instead of clear(), that limits you to 4 billion cache items as well.
+ *    E.g. If you use a "all" items tag for expiry instead of clear(), that limits you to 4 billion cache items also.
  *
  * @see https://redis.io/topics/lru-cache#eviction-policies Documentation for Redis eviction policies.
  * @see https://redis.io/topics/data-types#sets Documentation for Redis Set datatype.