docs: update options info

PR-URL: #31
Credit: @claudiahdz
Close: #31
Reviewed-by: @isaacs

Author: claudiahdz

README.md

@@ -33,7 +33,6 @@ just as easily be used on its own.
   * Writing
     * [`put`](#put-data)
     * [`put.stream`](#put-stream)
-    * [`put*` opts](#put-options)
     * [`rm.all`](#rm-all)
     * [`rm.entry`](#rm-entry)
     * [`rm.content`](#rm-content)
@@ -92,7 +91,7 @@ cacache.get.byDigest(cachePath, integrityHash).then(data => {
 * Lockless, high-concurrency cache access
 * Streaming support
 * Promise support
-* Pretty darn fast -- sub-millisecond reads and writes including verification
+* Fast -- sub-millisecond reads and writes including verification
 * Arbitrary metadata storage
 * Garbage collection and additional offline verification
 * Thorough test coverage
@@ -201,6 +200,8 @@ A sub-function, `get.byDigest` may be used for identical behavior, except lookup
 will happen by integrity hash, bypassing the index entirely. This version of the
 function *only* returns `data` itself, without any wrapper.
 
+See: [options](#get-options)
+
 ##### Note
 
 This function loads the entire cache entry into memory before returning it. If
@@ -242,6 +243,8 @@ A sub-function, `get.stream.byDigest` may be used for identical behavior,
 except lookup will happen by integrity hash, bypassing the index entirely. This
 version does not emit the `metadata` and `integrity` events at all.
 
+See: [options](#get-options)
+
 ##### Example
 
 ```javascript
@@ -328,12 +331,33 @@ cacache.get.hasContent(cachePath, 'sha521-NOT+IN/CACHE==').then(console.log)
 false
 ```
 
+##### <a name="get-options"></a> Options
+
+##### `opts.integrity`
+If present, the pre-calculated digest for the inserted content. If this option
+is provided and does not match the post-insertion digest, insertion will fail
+with an `EINTEGRITY` error.
+
+##### `opts.memoize`
+
+Default: null
+
+If explicitly truthy, cacache will read from memory and memoize data on bulk read. If `false`, cacache will read from disk data. Reader functions by default read from in-memory cache.
+
+##### `opts.size`
+If provided, the data stream will be verified to check that enough data was
+passed through. If there's more or less data than expected, insertion will fail
+with an `EBADSIZE` error.
+
+
 #### <a name="put-data"></a> `> cacache.put(cache, key, data, [opts]) -> Promise`
 
 Inserts data passed to it into the cache. The returned Promise resolves with a
 digest (generated according to [`opts.algorithms`](#optsalgorithms)) after the
 cache entry has been successfully written.
 
+See: [options](#put-options)
+
 ##### Example
 
 ```javascript
@@ -353,6 +377,8 @@ Stream](https://nodejs.org/api/stream.html#stream_writable_streams) that inserts
 data written to it into the cache. Emits an `integrity` event with the digest of
 written contents when it succeeds.
 
+See: [options](#put-options)
+
 ##### Example
 
 ```javascript
@@ -365,9 +391,7 @@ request.get(
 )
 ```
 
-#### <a name="put-options"></a> `> cacache.put options`
-
-`cacache.put` functions have a number of options in common.
+##### <a name="put-options"></a> Options
 
 ##### `opts.metadata`
 
@@ -382,7 +406,7 @@ with an `EBADSIZE` error.
 ##### `opts.integrity`
 
 If present, the pre-calculated digest for the inserted content. If this option
-if provided and does not match the post-insertion digest, insertion will fail
+is provided and does not match the post-insertion digest, insertion will fail
 with an `EINTEGRITY` error.
 
 `algorithms` has no effect if this option is present.
@@ -415,6 +439,11 @@ cache.
 Reading from disk data can be forced by explicitly passing `memoize: false` to
 the reader functions, but their default will be to read from memory.
 
+##### `opts.tmpPrefix`
+Default: null
+
+Prefix to append on the temporary directory name inside the cache's tmp dir. 
+
 #### <a name="rm-all"></a> `> cacache.rm.all(cache) -> Promise`
 
 Clears the entire cache. Mainly by blowing away the cache directory itself.
@@ -478,6 +507,8 @@ permissions.
 If you want automatic cleanup of this directory, use
 [`tmp.withTmp()`](#with-tpm)
 
+See: [options](#tmp-options)
+
 ##### Example
 
 ```javascript
@@ -517,6 +548,8 @@ promise completes.
 The same caveats apply when it comes to managing permissions for the tmp dir's
 contents.
 
+See: [options](#tmp-options)
+
 ##### Example
 
 ```javascript
@@ -527,6 +560,13 @@ cacache.tmp.withTmp(cache, dir => {
 })
 ```
 
+##### <a name="tmp-options"></a> Options
+
+##### `opts.tmpPrefix`
+Default: null
+
+Prefix to append on the temporary directory name inside the cache's tmp dir. 
+
 #### <a name="integrity"></a> Subresource Integrity Digests
 
 For content verification and addressing, cacache uses strings following the
@@ -582,10 +622,24 @@ When it's done, it'll return an object with various stats about the verification
 process, including amount of storage reclaimed, number of valid entries, number
 of entries removed, etc.
 
-##### Options
+##### <a name="verify-options"></a> Options
+
+##### `opts.concurrency`
+
+Default: 20
 
-* `opts.filter` - receives a formatted entry. Return false to remove it.
-                  Note: might be called more than once on the same entry.
+Number of concurrently read files in the filesystem while doing clean up.
+
+##### `opts.filter`
+Receives a formatted entry. Return false to remove it.
+Note: might be called more than once on the same entry.
+
+##### `opts.log`
+Custom logger function:
+```
+  log: { silly () {} }
+  log.silly('verify', 'verifying cache at', cache)
+```
 
 ##### Example