Merge pull request #19295 from abpframework/maliming-patch-3

Update Dependency-Injection.md

docs/en/Dependency-Injection.md

@@ -129,6 +129,7 @@ If you do not specify which services to expose, ABP expose services by conventio
 
 * The class itself is exposed by default. That means you can inject it by ``TaxCalculator`` class.
 * Default interfaces are exposed by default. Default interfaces are determined by naming convention. In this example, ``ICalculator`` and ``ITaxCalculator`` are default interfaces of ``TaxCalculator``, but ``ICanCalculate`` is not. A generic interface (e.g. `ICalculator<string>`) is also considered as a default interface if the naming convention is satisfied.
+* The resolved instances will be the same if multiple services are exposed for **Singleton** and **Scoped** services. This behavior requires exposing the class itself.
 
 ### Combining All Together
 
@@ -507,4 +508,4 @@ Startup templates come with Autofac installed. See [Autofac integration](Autofac
 ## See Also
 
 * [ASP.NET Core Dependency Injection Best Practices, Tips & Tricks](https://medium.com/volosoft/asp-net-core-dependency-injection-best-practices-tips-tricks-c6e9c67f9d96)
-* [Video tutorial](https://abp.io/video-courses/essentials/dependency-injection)
+* [Video tutorial](https://abp.io/video-courses/essentials/dependency-injection)