From 577673dcf768dc8d5a7b6190380286353ac44725 Mon Sep 17 00:00:00 2001 From: Sabareesh Kappagantu Date: Thu, 1 Sep 2022 20:11:22 -0600 Subject: [PATCH] docs: fix linting errors in change detection guide (#47324) PR Close #47324 --- aio/content/guide/change-detection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aio/content/guide/change-detection.md b/aio/content/guide/change-detection.md index 53aeea64172..371a294a586 100644 --- a/aio/content/guide/change-detection.md +++ b/aio/content/guide/change-detection.md @@ -1,6 +1,6 @@ # Angular change detection and runtime optimization -**Change detection** is the process through which Angular checks to see whether your application state has changed, and if any DOM needs to be updated. At a high level, Angular walks your components from top to bottom, looking for changes. Angular runs its change detection mechanism periodically so that changes to the data model are reflected in an app’s view. Change detection can be triggered either manually or through an asynchronous event (for example, a user interaction or an XHR completion). +**Change detection** is the process through which Angular checks to see whether your application state has changed, and if any DOM needs to be updated. At a high level, Angular walks your components from top to bottom, looking for changes. Angular runs its change detection mechanism periodically so that changes to the data model are reflected in an application’s view. Change detection can be triggered either manually or through an asynchronous event (for example, a user interaction or an XMLHttpRequest completion). Change detection is a highly optimized performant, but it can still cause slowdowns if the application runs it too frequently.