Add functional to logical description (#11263)

Based on the gap analysis.

website/content/docs/concepts/response-wrapping.mdx

@@ -26,9 +26,12 @@ To help address this problem, Vault includes a feature called _response
 wrapping_. When requested, Vault can take the response it would have sent to an
 HTTP client and instead insert it into the
 [`cubbyhole`](/docs/secrets/cubbyhole) of a single-use token,
-returning that single-use token instead. Logically speaking, the response is
+returning that single-use token instead.
+
+Logically speaking, the response is
 wrapped by the token, and retrieving it requires an unwrap operation against
-this token.
+this token. Functionally speaking, the token provides authorization to use
+an encryption key from Vault's keyring to decrypt the data.
 
 This provides a powerful mechanism for information sharing in many
 environments. In the types of scenarios, described above, often the best