From bcdb3ea8df6b47dad4b05c95705aada68a539231 Mon Sep 17 00:00:00 2001 From: Zhiwei Liang Date: Thu, 1 Oct 2026 13:14:29 -0400 Subject: [PATCH] fix(docs): link to the v3 versions of two pages from v3 docs The unversioned /key-value-store-tutorial and /manifest-reference-v1 paths redirect to /v4/, where those pages no longer exist. Signed-off-by: Zhiwei Liang --- content/v3/contributing-docs.md | 2 +- content/v3/triggers.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/v3/contributing-docs.md b/content/v3/contributing-docs.md index 207deca4..bf1b0d96 100644 --- a/content/v3/contributing-docs.md +++ b/content/v3/contributing-docs.md @@ -44,7 +44,7 @@ The following points will help guide your contribution from a resource-type pers ### 1. Tutorials -Tutorials are oriented toward learning. Tutorials are designed to get a user started on something new (that they have not tried before). You can think of a tutorial as a lesson i.e. teaching a Spin user [how to use the Key Value store to persist data](/key-value-store-tutorial.md). The tutorial may contain many logically ordered steps i.e. installing Spin, using Spin templates, configuring a Spin application and so forth. The desired outcome for a tutorial is for the user to have a working deployment or application. Think of it as a lesson in how to bake a cake. +Tutorials are oriented toward learning. Tutorials are designed to get a user started on something new (that they have not tried before). You can think of a tutorial as a lesson i.e. teaching a Spin user [how to use the Key Value store to persist data](/v3/key-value-store-tutorial.md). The tutorial may contain many logically ordered steps i.e. installing Spin, using Spin templates, configuring a Spin application and so forth. The desired outcome for a tutorial is for the user to have a working deployment or application. Think of it as a lesson in how to bake a cake. ### 2. How-To Guides diff --git a/content/v3/triggers.md b/content/v3/triggers.md index 459d96cb..619f6774 100644 --- a/content/v3/triggers.md +++ b/content/v3/triggers.md @@ -27,7 +27,7 @@ In Spin 2.2 and earlier, all triggers must be of the same type. For example, an In Spin 2.3 and later, an application can contain triggers of different types. For example, a single application can serve HTTP on one or more routes, and at the same time subscribe to one or more Redis pub-sub channels. -> If you're familiar with [Spin 1.x](/manifest-reference-v1#the-trigger-table), note that [Spin 2 uses the term "trigger"](/manifest-reference#the-trigger-table) to refer to each individual route or channel, rather than the trigger type. It's closer to the `[component.trigger]` usage than to the application trigger. +> If you're familiar with [Spin 1.x](/v3/manifest-reference-v1#the-trigger-table), note that [Spin 2 uses the term "trigger"](/manifest-reference#the-trigger-table) to refer to each individual route or channel, rather than the trigger type. It's closer to the `[component.trigger]` usage than to the application trigger. ## Triggers and Components