From 02da71c35cb0ec2c646e1377a68b537285a402b8 Mon Sep 17 00:00:00 2001
From: Sasidharan SD <sasidharaninfotech@gmail.com>
Date: Sun, 7 Jul 2024 22:37:47 +0530
Subject: [PATCH] docs: fix previous configuration link (#56880)

PR Close #56880
---
 adev/src/content/guide/testing/components-scenarios.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/adev/src/content/guide/testing/components-scenarios.md b/adev/src/content/guide/testing/components-scenarios.md
index c96dcf0a8f3..ab567f44472 100644
--- a/adev/src/content/guide/testing/components-scenarios.md
+++ b/adev/src/content/guide/testing/components-scenarios.md
@@ -1066,7 +1066,7 @@ Fortunately, the `HeroDetailService` delegates responsibility for remote data ac
 
 <docs-code header="app/hero/hero-detail.service.ts (prototype)" path="adev/src/content/examples/testing/src/app/hero/hero-detail.service.ts" visibleRegion="prototype"/>
 
-The [previous test configuration](#feature-module-import) replaces the real `HeroService` with a `TestHeroService` that intercepts server requests and fakes their responses.
+The [previous test configuration](#import-a-feature-module) replaces the real `HeroService` with a `TestHeroService` that intercepts server requests and fakes their responses.
 
 What if you aren't so lucky.
 What if faking the `HeroService` is hard?