From 4beaddcb8303db7a51c4850f3ef4cfe96bede087 Mon Sep 17 00:00:00 2001
From: Alison <agale753@gmail.com>
Date: Fri, 2 Oct 2020 14:39:08 -0700
Subject: [PATCH] docs(upgrade): expand upon change detection implications for
 downgraded components (#39100)

PR Close #39100
---
 aio/content/guide/upgrade.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/aio/content/guide/upgrade.md b/aio/content/guide/upgrade.md
index 93ec769c97..3293f4eb12 100644
--- a/aio/content/guide/upgrade.md
+++ b/aio/content/guide/upgrade.md
@@ -479,6 +479,15 @@ using the `downgradeComponent()` method. The result is an AngularJS
 <code-example path="upgrade-module/src/app/downgrade-static/app.module.ts" region="downgradecomponent" header="app.module.ts">
 </code-example>
 
+<div class="alert is-helpful">
+
+By default, Angular change detection will also run on the component for every
+AngularJS `$digest` cycle. If you wish to only have change detection run when
+the inputs change, you can set `propagateDigest` to `false` when calling
+`downgradeComponent()`.
+
+</div>
+
 Because `HeroDetailComponent` is an Angular component, you must also add it to the
 `declarations` in the `AppModule`.