Update capabilities.mdx

Signed-off-by: Eric Gregory <[email protected]>
wasmCloud · Jul 11, 2024 · 818067e · 818067e
1 parent 1d01ef7
commit 818067e
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/docs/concepts/capabilities.mdx b/docs/concepts/capabilities.mdx
@@ -26,7 +26,8 @@ Capabilities are enacted by an **interface** and one or more swappable **capabil
 
 For example...
 
-* The [Redis key-value storage provider](https://github.com/wasmCloud/wasmCloud/pkgs/container/keyvalue-redis) delivers the key-value capability to application components over the standard `wasi:keyvalue` API. 
+* The [Redis key-value storage provider](https://github.com/wasmCloud/wasmCloud/pkgs/container/keyvalue-redis) delivers the key-value capability to application components over the standard [`wasi:keyvalue`](https://github.com/WebAssembly/wasi-keyvalue/) API. 
+* The team can use the same `wasi:keyvalue` functions&mdash;for example, `get`, `set`, `delete`, and `exists`&mdash;regardless of your intended capability provider.
 * If the development team chooses to use Vault for key-value storage instead, they can swap out the Redis provider for the [Vault provider](https://github.com/wasmCloud/wasmCloud/pkgs/container/keyvalue-vault). 
 * The Vault capability provider will deliver a different implementation of the same capability *over the same API*.