From f2dc1013b3383c78599b9d3bb0d9d9cefaee29e7 Mon Sep 17 00:00:00 2001 From: itowlson Date: Tue, 14 Jul 2026 08:03:12 +1200 Subject: [PATCH] Fix misformatted link Signed-off-by: itowlson --- content/v4/kv-store-api-guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/v4/kv-store-api-guide.md b/content/v4/kv-store-api-guide.md index 0c593340..be64c08d 100644 --- a/content/v4/kv-store-api-guide.md +++ b/content/v4/kv-store-api-guide.md @@ -197,7 +197,7 @@ func example() error { ## Key Value Store Limits -The key/value size limits and syntactic requirements of a key value store depends on which [key value store provider](./dynamic-configuration#key-value-store-runtime-configuration) your app uses. The Spin command line currently supports a [default local SQLite provider]((./dynamic-configuration#file-key-value-store-provider)), a Redis KV provider, an Azure Cosmos DB backed provider, and an AWS Dynamo DB provider. See the [key value store runtime configuration](./dynamic-configuration#key-value-store-runtime-configuration) documentation for more information about the limits and requirements of each provider. +The key/value size limits and syntactic requirements of a key value store depends on which [key value store provider](./dynamic-configuration#key-value-store-runtime-configuration) your app uses. The Spin command line currently supports a [default local SQLite provider](./dynamic-configuration#file-key-value-store-provider), a Redis KV provider, an Azure Cosmos DB backed provider, and an AWS Dynamo DB provider. See the [key value store runtime configuration](./dynamic-configuration#key-value-store-runtime-configuration) documentation for more information about the limits and requirements of each provider. When you deploy your application, bear in mind that your deployment platform may have a KV provider with different characteristics from your local one!