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.
 
 <div class="lightbox">
   <img alt="Angular DevTools profiler preview showing Zone pollution" src="generated/images/guide/change-detection/zone-pollution.png">