Fixup docs

CHANGELOG.md

@@ -71,14 +71,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [v5.10.1] - 2023-06-09
 ### Added
-- `ParentDependency` flag for `ResolutionBehavior`. It indicates that parent containers (including indirect all ancestors) can only provide dependencies for services that are already selected for resolution.
+- `ParentDependency` flag for `ResolutionBehavior`. It indicates that parent containers (including all indirect ancestors) can only provide dependencies for services that are already selected for resolution.
 ### Fixed
 - During factory resolution, the type map check failed for registrations like: `.Register<IService>(c => c.WithFactory(/* ... */).AsServiceAlso<IAnother>())`. Now, the container gets the implementation type from the generic context where it's possible.
 
 ## [v5.10.0] - 2023-06-04
 ### Changed
 - Each `Resolve()` method now accepts a `ResolutionBehavior` flag parameter. It determines which level of the container hierarchy can take part in the service resolution. Possible values:
-  - `Parent`: Indicates that parent containers (including indirect all ancestors) can participate in the resolution request's service selection.
+  - `Parent`: Indicates that parent containers (including all indirect ancestors) can participate in the resolution request's service selection.
   - `Current`: Indicates that the current container (which initiated the resolution request) can participate in the service selection.
   - `Default`: The default behavior, it's used when the parameter is not specified. Its value is `Parent | Current`, so the parents and the current (which initiated the resolution request) container can participate in the resolution request's service selection.
 - `CreateChildContainer()` now accepts an `attachToParent` boolean parameter, which indicates whether the parent container's disposal should also dispose the child. It defaults to `true`.

docs/docs/advanced/child-containers.md

@@ -96,10 +96,10 @@ foreach (var child in container.ChildContainers)
 You can control which level of the container hierarchy can participate in the service resolution with the `ResolutionBehavior` parameter. 
 
 Possible values:
-- `Default`: The default behavior, it's used when the parameter is not specified. Its value is `Parent | Current`, so the parents and the current container (which initiated the resolution request) can participate in the resolution request's service selection.
-- `Parent`: Indicates that parent containers (including indirect all ancestors) can participate in the resolution request's service selection.
+- `Default`: The default behavior, it's used when the parameter is not specified. Its value is `Parent | Current`, so both the current container (which initiated the resolution request) and its parents can participate in the resolution request's service selection.
+- `Parent`: Indicates that parent containers (including all indirect ancestors) can participate in the resolution request's service selection.
 - `Current`: Indicates that the current container (which initiated the resolution request) can participate in the service selection.
-- `ParentDependency`: Indicates that parent containers (including indirect all ancestors) can only provide dependencies for services that are already selected for resolution.
+- `ParentDependency`: Indicates that parent containers (including all indirect ancestors) can only provide dependencies for services that are already selected for resolution.
 - `PreferEnumerableInCurrent`: Upon enumerable resolution, services from the current container (which initiated the resolution request) are preferred, ignoring services from parent containers.
 
 ```csharp

src/Resolution/ResolutionBehavior.cs

@@ -10,12 +10,12 @@ namespace Stashbox.Resolution;
 public enum ResolutionBehavior
 {
     /// <summary>
-    /// Indicates that both the parents and the current (which initiated the resolution request) container can participate in the resolution request's service selection.
+    /// Indicates that both the current container (which initiated the resolution request) and its parents can participate in the resolution request's service selection.
     /// </summary>
     Default = Current | Parent,
 
     /// <summary>
-    /// Indicates that parent containers (including indirect all ancestors) can participate in the resolution request's service selection.
+    /// Indicates that parent containers (including all indirect ancestors) can participate in the resolution request's service selection.
     /// </summary>
     Parent = 1 << 0,
 
@@ -25,7 +25,7 @@ public enum ResolutionBehavior
     Current = 1 << 1,
 
     /// <summary>
-    /// Indicates that parent containers (including indirect all ancestors) can only provide dependencies for services that are already selected for resolution.
+    /// Indicates that parent containers (including all indirect ancestors) can only provide dependencies for services that are already selected for resolution.
     /// </summary>
     ParentDependency = 1 << 2,