From 983aa233cf55c4cc80abf657063ef3ef6a541bb7 Mon Sep 17 00:00:00 2001 From: Roopesh Chinnakampalli Date: Tue, 24 May 2022 09:30:01 -0400 Subject: [PATCH] docs: corrected the misspelled word (#46126) innovation -> invocation PR Close #46126 --- aio/content/guide/change-detection-zone-pollution.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aio/content/guide/change-detection-zone-pollution.md b/aio/content/guide/change-detection-zone-pollution.md index a73f8e80ad9..25d73607055 100644 --- a/aio/content/guide/change-detection-zone-pollution.md +++ b/aio/content/guide/change-detection-zone-pollution.md @@ -10,7 +10,7 @@ This section covers how to identify such conditions, and how to run code outside ## Identifying unnecessary change detection calls -You can detect unnecessary change detection calls using Angular DevTools. Often they appear as consecutive bars in the profiler’s timeline with source `setTimeout`, `setInterval`, `requestAnimationFrame`, or an event handler. When you have limited calls within your application of these APIs, the change detection innovation is usually caused by a third-party library. +You can detect unnecessary change detection calls using Angular DevTools. Often they appear as consecutive bars in the profiler’s timeline with source `setTimeout`, `setInterval`, `requestAnimationFrame`, or an event handler. When you have limited calls within your application of these APIs, the change detection invocation is usually caused by a third-party library.
Angular DevTools profiler preview showing Zone pollution