Fix typos and improve readability in documentation

Author: Konstantin Tieber

NotModified/Annotation/ReplaceWithNotModifiedResponse.php

@@ -14,7 +14,7 @@
 use Webfactory\HttpCacheBundle\NotModified\VoterInterface;
 
 /**
- * This Annotation determines the last modified date over all of it's parameterising voters. This date is used by the
+ * This Annotation determines the last modified date over all of its parameterised voters. This date is used by the
  * \Webfactory\HttpCacheBundle\NotModified\EventListener to possibly replace the execution of a controller with
  * sending a Not Modified HTTP response.
  *

NotModified/EventListener.php

@@ -50,8 +50,8 @@ public function __construct(Reader $reader, ContainerInterface $container)
 
     /**
      * When the controller action for a request is determined, check it for a ReplaceWithNotModifiedResponse annotation.
-     * If it determines that the underlying ressources for the response were not modified after the "If-Modified-Since"
-     * header in the request, replace the determines controller action with an minimal action that just returns an
+     * If it determines that the underlying resources for the response were not modified after the "If-Modified-Since"
+     * header in the request, replace the determined controller action with a minimal action that just returns an
      * "empty" response with a 304 Not Modified HTTP status code.
      *
      * @param FilterControllerEvent $event

NotModified/VoterInterface.php

@@ -13,8 +13,8 @@
 
 /**
  * The ReplaceWithNotModifiedResponse method annotation is parameterised with Voters. Each Voter should determine the
- * last modified date of one of the various underlying ressources for a response. E.g. if your controller's indexAction
- * build a response containing News and Users, you can write a NewsVoter determining the date of the last published
+ * last modified date of one of the various underlying resources for a response. E.g. if your controller's indexAction
+ * builds a response containing News and Users, you can write a NewsVoter determining the date of the last published
  * News and a UserVoter determining the creation date of the last registered User.
  */
 interface VoterInterface

README.md

@@ -4,7 +4,7 @@ WebfactoryHttpCacheBundle is a Symfony bundle that eases
 [HTTP cache validation via the last modified header](https://symfony.com/doc/current/http_cache/validation.html#validation-with-the-last-modified-header).
 
 It provides the ```ReplaceWithNotModifiedResponse``` annotation for your controller actions. This annotation can be
-parameterised with Voters, one for each of the underlying ressources that overall determine the last modified date for
+parameterised with Voters, one for each of the underlying resources, and determines the overall latest "last modified" date for
 the response. If the client request contains an appropriate if-not-modified-since header, the execution of the
 controller action will be skipped and an empty response with a 304 Not Modified status code will be sent. If your Voters
 are fast, this can improve your performance greatly.
@@ -116,8 +116,8 @@ services:
 ```
 
 Although this seems to be more code, we find it to be a good deal, as we separate the concerns better and encapsulate
-the tasks in a smaller units that are easier to understand and test. Another advantage becomes obvious when we have
-another controller action that depends on an article for it's last modified date - we can reuse the ArticleVoter and
+the tasks into smaller units that are easier to understand and test. Another advantage becomes obvious when we have
+another controller action that depends on an article for its last modified date - we can reuse the ArticleVoter and
 combine it with other Voters.
 
 
@@ -208,7 +208,7 @@ final class MyController
 }
 ```
 
-The most simple form of adding a Voter is passing it's fully qualfified class name:
+The most simple form of adding a Voter is passing its fully qualfified class name:
 
     @ReplaceWithNotModifiedResponse(voters = {"\My\Namespace\MySimpleVoter"})