diff --git a/README.md b/README.md index efaa552e..e2cf2684 100644 --- a/README.md +++ b/README.md @@ -579,7 +579,7 @@ world .updateEach(([position, velocity]) => {}, { changeDetection: 'always' }) ``` -Changed detection shallowly compares the scalar values just like React. This means objects and arrays will only be detected as changed if a new object or array is committed to the store. While immutable state is a great design pattern, it creates memory pressure and reduces performance so instead you can mutate and manually flag that a changed has occured. +Changed detection shallowly compares the scalar values just like React. This means objects and arrays will only be detected as changed if a new object or array is committed to the store. While immutable state is a great design pattern, it creates memory pressure and reduces performance so instead you can mutate and manually flag that a change has occurred. ```js // ❌ This change will not be detected since the array is mutated and will pass the comparison diff --git a/docs/advanced/change-detection.md b/docs/advanced/change-detection.md index bae322c8..4a0092a6 100644 --- a/docs/advanced/change-detection.md +++ b/docs/advanced/change-detection.md @@ -18,7 +18,7 @@ world .updateEach(([position, velocity]) => {}, { changeDetection: 'always' }) ``` -Changed detection shallowly compares the scalar values just like React. This means objects and arrays will only be detected as changed if a new object or array is committed to the store. While immutable state is a great design pattern, it creates memory pressure and reduces performance so instead you can mutate and manually flag that a changed has occured. +Changed detection shallowly compares the scalar values just like React. This means objects and arrays will only be detected as changed if a new object or array is committed to the store. While immutable state is a great design pattern, it creates memory pressure and reduces performance so instead you can mutate and manually flag that a change has occurred. ```js // ❌ This change will not be detected since the array is mutated and will pass the comparison diff --git a/packages/publish/README.md b/packages/publish/README.md index 0c11f6bf..a65cb885 100644 --- a/packages/publish/README.md +++ b/packages/publish/README.md @@ -563,7 +563,7 @@ world .updateEach(([position, velocity]) => {}, { changeDetection: 'always' }) ``` -Changed detection shallowly compares the scalar values just like React. This means objects and arrays will only be detected as changed if a new object or array is committed to the store. While immutable state is a great design pattern, it creates memory pressure and reduces performance so instead you can mutate and manually flag that a changed has occured. +Changed detection shallowly compares the scalar values just like React. This means objects and arrays will only be detected as changed if a new object or array is committed to the store. While immutable state is a great design pattern, it creates memory pressure and reduces performance so instead you can mutate and manually flag that a change has occurred. ```js // ❌ This change will not be detected since the array is mutated and will pass the comparison