From c2909cd5eed024f6b36cf3c9dc9be248eedb3cc6 Mon Sep 17 00:00:00 2001 From: TheButlerM Date: Sun, 1 Mar 2026 09:58:08 +0100 Subject: [PATCH] =?UTF-8?q?fix:=20typo=20in=20Key=20Concepts=20page=20(con?= =?UTF-8?q?versatio=20=E2=86=92=20conversation)=20(#689)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixes #687 - Missing 'n' in the word 'conversation' in the Conversation Variables section. Co-authored-by: DebuggingMax --- en/use-dify/getting-started/key-concepts.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/en/use-dify/getting-started/key-concepts.mdx b/en/use-dify/getting-started/key-concepts.mdx index 7365b2dd..bb0c990f 100644 --- a/en/use-dify/getting-started/key-concepts.mdx +++ b/en/use-dify/getting-started/key-concepts.mdx @@ -116,7 +116,7 @@ Like inputs, node outputs cannot be updated either. **Environment Variables**: Use environment variable to store sensitive information like API keys specific to your app. This allows a clean separation between secrets and the Dify app itself, so you don't have to risk exposing passwords and keys when sharing your app's DSL. Environment variables are also constants and cannot be updated. -**Conversation Variables (Chatflow only)**: These variables are conversation-specific -- meaning they persist over multi-turn chatflow runs in a single conversatio so you can store and access dynamic information like to-do list and token cost. You can update the value of a conversation variable via the Variable Assigner node: +**Conversation Variables (Chatflow only)**: These variables are conversation-specific -- meaning they persist over multi-turn chatflow runs in a single conversation so you can store and access dynamic information like to-do list and token cost. You can update the value of a conversation variable via the Variable Assigner node: