From 248d382c79c5cd2cfb4303f119b01474a1b65321 Mon Sep 17 00:00:00 2001
From: Laforge Thomas <30832608+tomalaforge@users.noreply.github.com>
Date: Wed, 28 Dec 2022 14:26:57 +0100
Subject: [PATCH] feat(challenge12): update readme to add a video

---
 apps/scroll-cd/README.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/apps/scroll-cd/README.md b/apps/scroll-cd/README.md
index 807c7c8..3692c7b 100644
--- a/apps/scroll-cd/README.md
+++ b/apps/scroll-cd/README.md
@@ -6,15 +6,16 @@
 
 In this challenge, you will need to optimize the change detection cycles run by Angular.
 
-Zone.js will trigger a change detection cycle each time a scroll event is dispatched. However we only want to show or hide a button at a specific scroll position. Therefore, we only want to refresh our application once.
+Zone.js triggers a change detection cycle each time a scroll event is dispatched. However we only want to show or hide a button at a specific scroll position. Therefore, we only want to refresh our application once.
 
 > You can vizualise how many times CD is triggered by installing the [Angular chrome devTool](https://chrome.google.com/webstore/detail/angular-devtools/ienfalfjdbdpebioblfackkekamfmbnh) and starting a new recording on the profiler tab.
 
 The following video will explain what is the goal of this challenge.
+https://user-images.githubusercontent.com/30832608/209819211-58d9ddcf-e1ad-4a78-8a7a-2be9d729e3f1.mov
 
 ### Statement
 
-Your goal for this challenge is to avoid all those unnecessary change detection cycle and trigger a CD only when needed.
+Your goal for this challenge is to avoid all unnecessary change detection cycles and trigger a CD only when needed.
 
 #### Constraint: