From 193ec0de86f8d5fc5cc02179b9b8af9b3a68a2d9 Mon Sep 17 00:00:00 2001 From: Aki Hamano <54422211+t-hamano@users.noreply.github.com> Date: Mon, 23 Dec 2024 22:50:00 +0900 Subject: [PATCH] Update docs/reference-guides/interactivity-api/core-concepts/using-typescript.md --- .../interactivity-api/core-concepts/using-typescript.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference-guides/interactivity-api/core-concepts/using-typescript.md b/docs/reference-guides/interactivity-api/core-concepts/using-typescript.md index bc2fde0dc66bf0..4e4ab7cb1038ed 100644 --- a/docs/reference-guides/interactivity-api/core-concepts/using-typescript.md +++ b/docs/reference-guides/interactivity-api/core-concepts/using-typescript.md @@ -269,7 +269,7 @@ That's it! Now you can access the context properties with the correct types. The derived state is data that is calculated based on the global state or local context. In the client store definition, it is defined using a getter in the `state` object. -_Please, visit the [Understanding global state, local context and derived state](./understanding-global-state-local-context-and-derived-state.md) guide to learn more about how derived state works in the Interactivity API._ +_Please, visit the [Understanding global state, local context and derived state](./undestanding-global-state-local-context-and-derived-state.md) guide to learn more about how derived state works in the Interactivity API._ Following our previous example, let's create a derived state that is the double of our counter.