From 1579bf36e8c0fd6bd7807f3648b70dde8352923b Mon Sep 17 00:00:00 2001 From: Josh Soref Date: Wed, 6 Sep 2017 05:46:23 +0000 Subject: [PATCH] spelling: changed --- lib/mixins/property-effects.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/mixins/property-effects.html b/lib/mixins/property-effects.html index be7118c239..edd30a0d17 100644 --- a/lib/mixins/property-effects.html +++ b/lib/mixins/property-effects.html @@ -1413,7 +1413,7 @@ * The dirty-check is important to prevent cycles due to two-way * notification, but paths and objects are only dirty checked against any * previous value set during this turn via a "temporary cache" that is - * cleared when the last `_propertiesChaged` exits. This is so: + * cleared when the last `_propertiesChanged` exits. This is so: * a. any cached array paths (e.g. 'array.3.prop') may be invalidated * due to array mutations like shift/unshift/splice; this is fine * since path changes are dirty-checked at user entry points like `set`