fix wording (mostly in docs)

doc/01-Basic-Menus.md

@@ -2,7 +2,7 @@
 
 Let's face it, creating menus sucks. Menus - a common aspect of any
 site - can range from being simple and mundane to giant monsters that
-become a headache to code and maintain.
+becomes a headache to code and maintain.
 
 This bundle solves the issue by giving you a small, yet powerful and flexible
 framework for handling your menus. While most of the examples shown here
@@ -13,7 +13,7 @@ are simple, the menus can grow arbitrarily large and deep.
 The menu framework centers around one main interface: `Knp\Menu\ItemInterface`.
 Items are created by a factory implementing `Knp\Menu\FactoryInterface`.
 It's best to think of each `ItemInterface` object as an `<li>` tag that can
-hold children objects (`<li>` tags that are wrapped in a `<ul>` tag).
+hold child objects (`<li>` tags that are wrapped in a `<ul>` tag).
 For example:
 
 ```php
@@ -53,13 +53,13 @@ The above would render the following html code:
 >The menu framework automatically adds `first` and `last` classes to each
 >`<li>` tag at each level for easy styling. Notice also that a `current`
 >class is added to the "current" menu item by URI and `current_ancestor`
->to its ancestors (the classes are configurable) The above example assumes
+>to its ancestors (the classes are configurable). The above example assumes
 >the menu is being rendered on the `/comments` page, making the Comments
 >menu the "current" item.
 
 When the menu is rendered, it's actually spaced correctly so that it appears
 as shown in the source HTML. This is to allow for easier debugging and can
-be turned off by passing the `true` as the second argument to the renderer.
+be turned off by passing `true` as the second argument to the renderer.
 
 ```php
 <?php

doc/04-Iterators.md

@@ -139,7 +139,7 @@ foreach ($iterator as $item) {
 ## Filtering only displayed items
 
 The `Knp\Menu\Iterator\DisplayedItemFilterIterator` allows you to filter
-items to keep only displayed ones. As hiding an item also hides its children,
+items to keep only the displayed ones. As hiding an item also hides its children,
 this filter is a recursive filter iterator and is applied on the recursive
 iterator, not on the flattened iterator.
 

doc/05-Matcher.md

@@ -46,7 +46,7 @@ class MyAwesomeVoter implements VoterInterface
 }
 ```
 
-Note: You can also write your own *matcher* that implements the `MatcherInterface`
-if you need something different than the voter approach.
+Note: You can also write your own *matcher* that implements the `MatcherInterface`,
+if you need something different from the voter approach.
 
 If you use the [KnpMenuBundle](https://symfony.com/bundles/KnpMenuBundle/current/index.html), the RouteVoter is automatically loaded.

doc/examples/01_apply_active_class_to_whole_tree.md

@@ -1,7 +1,7 @@
-# How to apply the active class to a item and all ancestors
+# How to apply the active class to an item and all ancestors
 
-By default the active menu item is applied with a `current` class and its ancestors are applied with a `current_ancestor` 
-class. To apply a class other than the default or apply the same class to both you can either pass it as an option to the 
+By default, the active menu item is applied with a `current` class and its ancestors are applied with a `current_ancestor` 
+class. To apply a class other than the default or apply the same class to both, you can either pass it as an option to the 
 render method of your used renderer:
 
 ```php

src/Knp/Menu/Renderer/RendererProviderInterface.php

@@ -9,7 +9,7 @@ interface RendererProviderInterface
      *
      * If null is given, a renderer marked as default is returned.
      *
-     * @throws \InvalidArgumentException if the renderer does not exists
+     * @throws \InvalidArgumentException if the renderer does not exist
      */
     public function get(?string $name = null): RendererInterface;