More container guidance

nservicebus/dependency-injection/index_ownership_core_[8.0,).partial.md

@@ -77,3 +77,9 @@ The [NServiceBus.Extensions.DependencyInjection Usage sample](/samples/dependenc
 ## Microsoft Generic Host
 
 When hosting NServiceBus with the [Microsoft Generic Host](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/generic-host) using the `NServiceBus.Extensions.Hosting` package, refer to the [configure custom containers documentation](/nservicebus/hosting/extensions-hosting.md#dependency-injection-integration-configure-custom-containers) for further details.
+
+## Resolving dependencies
+
+It is recommended to follow the [dependency injection guidelines](https://learn.microsoft.com/en-us/dotnet/core/extensions/dependency-injection-guidelines) for .NET. Be aware of the following special cases with NServiceBus:
+
+- [Injecting dependencies into behaviors](/nservicebus/pipeline/manipulate-with-behaviors.md)

nservicebus/pipeline/manipulate-with-behaviors.md

@@ -93,6 +93,8 @@ snippet: InjectingDependencies
 
 Dependencies injected into the constructor of a behavior become singletons regardless of their actual scope on the dependency injection container. In order to create instances per request or scoped dependencies it is required to use the builder that is available on the context.
 
+The builder on the context can vary depending on the pipeline stage it is being used in. For every [pipeline stage used within the context of an incoming message](/nservicebus/pipeline/steps-stages-connectors.md#stages-incoming-pipeline-stages) the builder exposes the child service provider created for the incoming message. For all other cases the builder exposes the root service provider. Behaviors in the [outgoing pipeline stage](/nservicebus/pipeline/steps-stages-connectors.md#stages-outgoing-pipeline-stages) exhibit different behaviors depending on how they are invoked. For example when an outgoing behavior is invoked from the context of a message session the builder exposes the root service provider. In cases when the same outgoing behavior is invoked from a message operation within the scope of an incoming message, the builder will be the child service provider for the incoming message.
+
 partial: options
 
 include: mutators-versus-behaviors