From 83405a36d3bb541534f6955e8cc63405baceccdb Mon Sep 17 00:00:00 2001 From: Sharon Lau Date: Mon, 7 Mar 2022 22:38:50 +0800 Subject: [PATCH] Remove redundancy in reactivity-fundamentals.md The clause following the 3rd "or" is redundant and may cause confusion. Removing it will make the explanation better match the code example. --- src/guide/essentials/reactivity-fundamentals.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guide/essentials/reactivity-fundamentals.md b/src/guide/essentials/reactivity-fundamentals.md index e22a7b3271..83bc8d4ab2 100644 --- a/src/guide/essentials/reactivity-fundamentals.md +++ b/src/guide/essentials/reactivity-fundamentals.md @@ -352,7 +352,7 @@ The `reactive()` API has two limitations: state = reactive({ count: 1 }) ``` - It also means that when we assign or destructure a reactive object's property into local variables, or when we pass that property into a function, or destructure properties from a reactive object, we will lose the reactivity connection: + It also means that when we assign or destructure a reactive object's property into local variables, or when we pass that property into a function, we will lose the reactivity connection: ```js const state = reactive({ count: 0 })