From 90313718d1890ba575b86bc04c95181f41498e93 Mon Sep 17 00:00:00 2001
From: Kirk Larkin <6025110+serpent5@users.noreply.github.com>
Date: Mon, 31 Aug 2020 05:59:37 +0100
Subject: [PATCH] Fix up recommendation re scope validation (#19719)

---
 aspnetcore/fundamentals/dependency-injection.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/aspnetcore/fundamentals/dependency-injection.md b/aspnetcore/fundamentals/dependency-injection.md
index f644a0f9cc..769fc4cffc 100644
--- a/aspnetcore/fundamentals/dependency-injection.md
+++ b/aspnetcore/fundamentals/dependency-injection.md
@@ -503,7 +503,7 @@ The factory method of single service, such as the second argument to [AddSinglet
   [!code-csharp[](dependency-injection/samples/3.x/AntiPattern3/Startup.cs?name=snippet)]
 
 * Disposable transient services are captured by the container for disposal. This can turn into a memory leak if resolved from the top level container.
-* Enable scope validation to make sure the app doesn't have scoped services that capture singletons. For more information, see [Scope validation](#scope-validation).
+* Enable scope validation to make sure the app doesn't have singletons that capture scoped services. For more information, see [Scope validation](#scope-validation).
 
 Like all sets of recommendations, you may encounter situations where ignoring a recommendation is required. Exceptions are rare, mostly special cases within the framework itself.