Do not repeat ourselves in the class but rather hint to the README

Author: Toflar

README.md

@@ -108,18 +108,20 @@ passing an array of `$options` in the constructor:
   **Type**: `int`
   **Default**: `500`
 
-* **cache_tags_header**: The HTTP header name used to check for tags
+* **cache_tags_header**: The HTTP header name that's used to check for tags.
 
   **Type**: `string`
   **Default**: `Cache-Tags`
 
 ### Caching `BinaryFileResponse` instances
 
-This cache implementation allows to cache `BinaryFileResponse` instances but the files are not actually copied to
-the cache directory. It will just try to fetch the original file and if that does not exist anymore, the store returns
+This cache implementation allows to cache `BinaryFileResponse` instances but
+the files are not actually copied to the cache directory. It will just try to
+fetch the original file and if that does not exist anymore, the store returns
 `null`, causing HttpCache to deal with it as a cache miss and continue normally.
-It is ideal for use cases such as caching `/favicon.ico` requests where you would like to prevent the application from
-being started and thus deliver the response from HttpCache.
+It is ideal for use cases such as caching `/favicon.ico` requests where you would
+like to prevent the application from being started and thus deliver the response
+from HttpCache.
 
 ### Cache tagging
 

src/Psr6Store.php

@@ -71,44 +71,7 @@ class Psr6Store implements Psr6StoreInterface, ClearableInterface
 
     /**
      * When creating a Psr6Store you can configure a number options.
-     *
-     * Either cache_directory or cache and lock_factory are required. If you
-     * want to set a custom cache / lock_factory, please **read the warning in
-     * the README first**.
-     *
-     * - cache_directory:   Path to the cache directory for the default cache
-     *                      adapter and lock factory.
-     *
-     * - cache:             Explicitly specify the cache adapter you want to
-     *                      use. Note that if you want to make use of cache
-     *                      tagging, this cache must implement the
-     *                      Symfony\Component\Cache\Adapter\TagAwareAdapterInterface
-     *
-     *                      Make sure that lock and cache have the same
-     *                      scope. *Read the warning in the README!*
-     *
-     *                      Type: Symfony\Component\Cache\Adapter\AdapterInterface
-     *
-     * - lock_factory:      Explicitly specify the cache adapter you want to
-     *                      use. Make sure that lock and cache have the same
-     *                      scope. *Read the warning in the README!*
-     *
-     *                      Type: Symfony\Component\Lock\Factory
-     *                      Default: Factory with SemaphoreStore if available,
-     *                               FlockStore otherwise.
-     *
-     * - prune_threshold:   Configure the number of write actions until the
-     *                      store will prune the expired cache entries. Pass
-     *                      0 to disable automated pruning.
-     *
-     *                      Type: int
-     *                      Default: 500
-     *
-     * - cache_tags_header: Name of HTTP header containing a comma separated
-     *                      list of tags to tag the response with.
-     *
-     *                      Type: string
-     *                      Default: Cache-Tags
+     * See the README for a list of all available options and their description.
      */
     public function __construct(array $options = [])
     {
@@ -550,7 +513,7 @@ private function isBinaryFileResponseContentDigest($digest)
     }
 
     /**
-     * Increases a counter every time an item is stored to the cache and then
+     * Increases a counter every time a write action is performed and then
      * prunes expired cache entries if a configurable threshold is reached.
      * This only happens during write operations so cache retrieval is not
      * slowed down.