@@ -93,7 +93,7 @@ passing an array of `$options` in the constructor:
9393 ** Type** : ` string `
9494 ** Default** : ` Cache-Tags `
9595
96- ### Cache Tagging
96+ ### Cache tagging
9797
9898Tag cache entries by adding a response header with the tags as a comma
9999separated value. By default, that header is called ` Cache-Tags ` , this can be
@@ -103,17 +103,19 @@ To invalidate tags, call the method `Psr6Store::invalidateTags` or use the
103103` PurgeTagsListener ` from the [ FOSHttpCache] [ 3 ] library to handle tag
104104invalidation requests.
105105
106- ### Pruning Expired Cache Entries
106+ ### Pruning expired cache entries
107107
108- By default, this cache removes expired entries from the cache after every 500
109- cache write operations. You can change the frequency with the ` prune_threshold `
108+ By default, this store removes expired entries from the cache after every ` 500 `
109+ cache ** write** operations. Fetching data does not affect performance.
110+ You can change the automated pruning frequency with the ` prune_threshold `
110111configuration setting.
111112
112113You can also manually trigger pruning by calling the ` prune() ` method on the
113- cache. With this, you could for example implement a cronjob that loads the store
114+ cache. With this, you could for example implement a cron job that loads the store
114115and prunes it at a configured interval, to prevent slowing down random requests
115116that were cache misses because they have to wait for the pruning to happen. If you
116- have set up a cron job, you should disable pruning by setting the threshold to 0.
117+ have set up a cron job, you should disable auto pruning by setting the threshold
118+ to ` 0 ` .
117119
118120### WARNING
119121
0 commit comments