From add5662075a3a1fcc2e777ff10137ad9d04fad33 Mon Sep 17 00:00:00 2001
From: Ernest Owusu Darko <117347727+eodAmalitech@users.noreply.github.com>
Date: Thu, 13 Apr 2023 15:33:49 +0000
Subject: [PATCH] Update dependency_management.md

documentation update: correction, of controller 1 is lost and hence it is removed
---
 documentation/en_US/dependency_management.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/en_US/dependency_management.md b/documentation/en_US/dependency_management.md
index c701ec1e6..7a62f4157 100644
--- a/documentation/en_US/dependency_management.md
+++ b/documentation/en_US/dependency_management.md
@@ -239,7 +239,7 @@ First, let's of the `fenix` of Get.lazyPut and the `permanent` of the other meth
 The fundamental difference between `permanent` and `fenix` is how you want to store your instances.
 
 Reinforcing: by default, GetX deletes instances when they are not in use.
-It means that: If screen 1 has controller 1 and screen 2 has controller 2 and you remove the first route from stack, (like if you use `Get.off()` or `Get.offNamed()`) the controller 1 lost its use so it will be erased.
+It means that: If screen 1 has controller 1 and screen 2 has controller 2 and you remove the first route from stack, (like if you use `Get.off()` or `Get.offNamed()`) the controller 1 is lost and so it will be removed.
 
 But if you want to opt for using `permanent:true`, then the controller will not be lost in this transition - which is very useful for services that you want to keep alive throughout the entire application.