fix typos

Author: BafS

README.md

@@ -4,7 +4,7 @@
 [![Total Downloads](https://poser.pugx.org/container-interop/container-interop/downloads.svg)](https://packagist.org/packages/container-interop/container-interop)
 
 *container-interop* tries to identify and standardize features in *container* objects (service locators,
-dependency injection containers, etc.) to achieve interopererability.
+dependency injection containers, etc.) to achieve interoperability.
 
 Through discussions and trials, we try to create a standard, made of common interfaces but also recommendations.
 

docs/ContainerInterface.md

@@ -11,8 +11,8 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
 interpreted as described in [RFC 2119][].
 
 The word `implementor` in this document is to be interpreted as someone
-implementing the `ContainerInterface` in a depency injection-related library or framework.
-Users of dependency injections containers (DIC) are refered to as `user`.
+implementing the `ContainerInterface` in a dependency injection-related library or framework.
+Users of dependency injections containers (DIC) are referred to as `user`.
 
 [RFC 2119]: http://tools.ietf.org/html/rfc2119
 
@@ -31,50 +31,50 @@ Users of dependency injections containers (DIC) are refered to as `user`.
   `user` SHOULD NOT rely on getting the same value on 2 successive calls.
   While `ContainerInterface` only defines one mandatory parameter in `get()`, implementations
   MAY accept additional optional parameters.
-  
+
 - `has` takes one unique parameter: an entry identifier. It MUST return `true`
   if an entry identifier is known to the container and `false` if it is not.
-  
+
 ### 1.2 Exceptions
 
-Exceptions directly thrown by the container MUST implement the 
+Exceptions directly thrown by the container MUST implement the
 [`Interop\Container\Exception\ContainerException`](../src/Interop/Container/Exception/ContainerException.php).
 
 A call to the `get` method with a non-existing id SHOULD throw a
 [`Interop\Container\Exception\NotFoundException`](../src/Interop/Container/Exception/NotFoundException.php).
 
 ### 1.3 Additional features
 
-This section describes additional features that MAY be added to a container. Containers are not 
+This section describes additional features that MAY be added to a container. Containers are not
 required to implement these features to respect the ContainerInterface.
 
 #### 1.3.1 Delegate lookup feature
 
-The goal of the *delegate lookup* feature is to allow several containers to share entries. 
+The goal of the *delegate lookup* feature is to allow several containers to share entries.
 Containers implementing this feature can perform dependency lookups in other containers.
 
-Containers implementing this feature will offer a greater lever of interoperability 
+Containers implementing this feature will offer a greater lever of interoperability
 with other containers. Implementation of this feature is therefore RECOMMENDED.
 
 A container implementing this feature:
 
 - MUST implement the `ContainerInterface`
-- MUST provide a way to register a delegate container (using a constructor parameter, or a setter, 
+- MUST provide a way to register a delegate container (using a constructor parameter, or a setter,
   or any possible way). The delegate container MUST implement the `ContainerInterface`.
 
 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. 
-  If the entry is not part of the container, an exception should be thrown 
+- 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`).
 - 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 
+- 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.
 
-It is however allowed for containers to provide exception cases for special entries, and a way to lookup 
+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

docs/Delegate-lookup.md

@@ -3,10 +3,10 @@ Delegate lookup feature
 
 This document describes a standard for dependency injection containers.
 
-The goal set by the *delegate lookup* feature is to allow several containers to share entries. 
+The goal set by the *delegate lookup* feature is to allow several containers to share entries.
 Containers implementing this feature can perform dependency lookups in other containers.
 
-Containers implementing this feature will offer a greater lever of interoperability 
+Containers implementing this feature will offer a greater lever of interoperability
 with other containers. Implementation of this feature is therefore RECOMMENDED.
 
 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
@@ -15,7 +15,7 @@ interpreted as described in [RFC 2119][].
 
 The word `implementor` in this document is to be interpreted as someone
 implementing the delegate lookup feature in a dependency injection-related library or framework.
-Users of dependency injections containers (DIC) are refered to as `user`.
+Users of dependency injections containers (DIC) are referred to as `user`.
 
 [RFC 2119]: http://tools.ietf.org/html/rfc2119
 
@@ -36,22 +36,22 @@ fetching the dependencies from.
 A container implementing the *delegate lookup* feature:
 
 - MUST implement the [`ContainerInterface`](ContainerInterface.md)
-- MUST provide a way to register a delegate container (using a constructor parameter, or a setter, 
+- MUST provide a way to register a delegate container (using a constructor parameter, or a setter,
   or any possible way). The delegate container MUST implement the [`ContainerInterface`](ContainerInterface.md).
 
 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.
-  If the entry is not part of the container, an exception should be thrown 
+  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 
+- 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 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 
+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.
 
 3. Package / Interface