From c94439f5f27f040bb142782bae5e91a8424763f8 Mon Sep 17 00:00:00 2001 From: Pete Cockerell <105939946+petercockerell-brt@users.noreply.github.com> Date: Sat, 2 Nov 2024 20:45:19 -0700 Subject: [PATCH] Added a missing word in fine-grained-reactivity.mdx (#942) --- src/routes/advanced-concepts/fine-grained-reactivity.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/routes/advanced-concepts/fine-grained-reactivity.mdx b/src/routes/advanced-concepts/fine-grained-reactivity.mdx index 55f430c66..7907f064c 100644 --- a/src/routes/advanced-concepts/fine-grained-reactivity.mdx +++ b/src/routes/advanced-concepts/fine-grained-reactivity.mdx @@ -73,7 +73,7 @@ The effect takes a function that is called whenever _any_ of the signals it reli To grasp the concept of reactivity, it is often helpful to construct a reactive system from scratch. The following example will follow the observer pattern, where data entities (signals) will maintain a list of their subscribers (effects). -This is a way to notify subscribers whenever a signal they changes. +This is a way to notify subscribers whenever a signal they observe changes. Here is a basic code outline to begin: