From c5f8f7a55a1467fd5529987227cdb3e6ba157ee5 Mon Sep 17 00:00:00 2001
From: Christian C <81857739+cibucristi@users.noreply.github.com>
Date: Sat, 20 Jan 2024 12:39:28 +0200
Subject: [PATCH] Updated Angular's documentation link to Angular's new dev
 docs.

---
 content/components.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/components.md b/content/components.md
index 66deda14ab..f714d3d9d2 100644
--- a/content/components.md
+++ b/content/components.md
@@ -112,7 +112,7 @@ The `CatsService` is **injected** through the class constructor. Notice the use
 
 #### Dependency injection
 
-Nest is built around the strong design pattern commonly known as **Dependency injection**. We recommend reading a great article about this concept in the official [Angular](https://angular.io/guide/dependency-injection) documentation.
+Nest is built around the strong design pattern commonly known as **Dependency injection**. We recommend reading a great article about this concept in the official [Angular](https://angular.dev/guide/di) documentation.
 
 In Nest, thanks to TypeScript capabilities, it's extremely easy to manage dependencies because they are resolved just by type. In the example below, Nest will resolve the `catsService` by creating and returning an instance of `CatsService` (or, in the normal case of a singleton, returning the existing instance if it has already been requested elsewhere). This dependency is resolved and passed to your controller's constructor (or assigned to the indicated property):