From fbc957552c006dbf277db94d4cef7097005b17d7 Mon Sep 17 00:00:00 2001
From: "J. Degand" <70610011+jdegand@users.noreply.github.com>
Date: Sun, 1 Sep 2024 00:33:37 -0400
Subject: [PATCH] docs(angular): update router events content (#6918)

---
 .../angular/content/router-events@YF_sG292HqawIX0siWhrv.md     | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/src/data/roadmaps/angular/content/router-events@YF_sG292HqawIX0siWhrv.md b/src/data/roadmaps/angular/content/router-events@YF_sG292HqawIX0siWhrv.md
index f8e57ceb6..d76d10e48 100644
--- a/src/data/roadmaps/angular/content/router-events@YF_sG292HqawIX0siWhrv.md
+++ b/src/data/roadmaps/angular/content/router-events@YF_sG292HqawIX0siWhrv.md
@@ -2,5 +2,8 @@
 
 The Angular Router raises events when it navigates from one route to another route. It raises several events such as `NavigationStart`, `NavigationEnd`, `NavigationCancel`, `NavigationError`, `ResolveStart`, etc. You can listen to these events and find out when the state of the route changes. Some of the useful events are route change start (NavigationStart) and route change end (NavigationEnd).
 
+Visit the following resources to learn more:
+
 - [@official@Router reference - Router events](https://angular.dev/guide/routing/router-reference#router-events)
 - [@official@Router event - API](https://angular.dev/api/router/RouterEvent)
+- [@article@Router events in Angular](https://medium.com/@gurunadhpukkalla/router-events-in-angular-3112a3968660)
\ No newline at end of file