Very minor changes

Author: mnapoli

docs/Delegate-lookup-meta.md

@@ -178,8 +178,7 @@ class CompositeContainer {
 
 Cons have been extensively discussed [here](https://github.com/container-interop/container-interop/pull/8#issuecomment-51721777).
 Basically, forcing a setter into an interface is a bad idea. Setters are similar to constructor arguments,
-and it's a bad idea to standardize a constructor.
-This outweights the benefits of the interface.
+and it's a bad idea to standardize a constructor: how the delegate container is configured into a container is an implementation detail. This outweights the benefits of the interface.
 
 ### 4.4 Alternative: no exception case for delegate lookups
 

docs/Delegate-lookup.md

@@ -24,6 +24,7 @@ Users of dependency injections containers (DIC) are refered to as `user`.
 
 In a dependency injection container, the container is used to fetch entries.
 Entries can have dependencies on other entries. Usually, these other entries are fetched by the container.
+
 The *delegate lookup* feature is the ability for a container to fetch dependencies in
 another container. In the rest of the document, the word "container" will reference the container
 implemented by the implementor. The word "delegate container" will reference the container we are
@@ -40,20 +41,20 @@ A container implementing the *delegate lookup* feature:
 
 When a container is configured to use a delegate container for dependencies:
 
-- Calls to the `get` method should only return an entry if the entry is part of the container. 
+- Calls to the `get` method should only return an entry if the entry is part of the container.
   If the entry is not part of the container, an exception should be thrown 
   (as requested by the [`ContainerInterface`](ContainerInterface.md)).
 - Calls to the `has` method should only return `true` if the entry is part of the container.
   If the entry is not part of the container, `false` should be returned.
 - If the fetched entry has dependencies, **instead** of performing 
   the dependency lookup in the container, the lookup is performed on the *delegate container*.
 
-Important! By default, the lookup SHOULD be performed on the delegate container **only**, not on the container itself.
+Important: By default, the dependency lookups SHOULD be performed on the delegate container **only**, not on the container itself.
 
 It is however allowed for containers to provide exception cases for special entries, and a way to lookup 
 into the same container (or another container) instead of the delegate container.
 
-2. Package / Interface
+3. Package / Interface
 ----------------------
 
-This feature is not tied to any interface or package.
+This feature is not tied to any code, interface or package.