Fix typos

pgrimaud · lchrusciel · commit fd50e9210155 · 2020-04-27T12:44:17.000+02:00
diff --git a/UPGRADE-1.0.md b/UPGRADE-1.0.md
@@ -179,7 +179,7 @@
 
 ### Order / OrderBundle
 
-* In order to be compatibile with Doctrine ORM 2.6+ and be more consistent,
+* In order to be compatible with Doctrine ORM 2.6+ and be more consistent,
   `OrderRepositoryInterface::count()` signature was changed to `OrderRepositoryInterface::countPlacedOrders()`.
   
 * The following methods no longer have a default null argument and require one to be explicitly passed:
diff --git a/UPGRADE-1.3.md b/UPGRADE-1.3.md
@@ -7,7 +7,7 @@
 
 * MongoDB and PHPCR drivers have been deprecated in `ResourceBundle` and `GridBundle`.
 
-* Refering to any file from `vendor/sylius/sylius/app` directory has been deprecated.
+* Referring to any file from `vendor/sylius/sylius/app` directory has been deprecated.
 
 ## Application
 
diff --git a/docs/api/taxons.rst b/docs/api/taxons.rst
@@ -933,7 +933,7 @@ Set position of product in a Taxon
 
 The products in Sylius can by grouped by taxon, therefore for every product there is a relation between the product and the assigned taxon.
 What is more, every product can have a specific position in the taxon to which it belongs. To put products in a specific order
-you will need to call the ``/api/v1/taxons/{code}/products`` endpoint wih the ``PUT`` method.
+you will need to call the ``/api/v1/taxons/{code}/products`` endpoint with the ``PUT`` method.
 
 Definition
 ^^^^^^^^^^
diff --git a/docs/book/customers/customer_pools.rst b/docs/book/customers/customer_pools.rst
@@ -37,7 +37,7 @@ The configuration looks like that:
                                    code: "default"
 
 Customer Pool can be assigned to a Channel, but only during its _creation_ in Admin panel. Currently it is not possible
-to modify the User Pool after the channel is created, as it would lead to certain edge cases with customers loosing access to channels,
+to modify the User Pool after the channel is created, as it would lead to certain edge cases with customers losing access to channels,
 after improper admin operations.
 
 There is also a possibility to choose a specific customer pool during channel or shop customer creation in fixtures
diff --git a/docs/book/installation/sylius_plus_installation.rst b/docs/book/installation/sylius_plus_installation.rst
@@ -325,7 +325,7 @@ your application's ``.env`` file:
     WKHTMLTOPDF_PATH=/your-path
     ###< knplabs/knp-snappy-bundle ###
 
-**10.** Copy templates that are overriden by Sylius Plus into ``templates/bundles``:
+**10.** Copy templates that are overridden by Sylius Plus into ``templates/bundles``:
 
 .. code-block:: bash
 
diff --git a/docs/book/organization/backward-compatibility-promise.rst b/docs/book/organization/backward-compatibility-promise.rst
@@ -77,7 +77,7 @@ Neither template events, block or templates themselves cannot be deleted or rena
 Deprecations
 ------------
 
-Before we remove or replace code covered by this backwards compatiblity promise, it is
+Before we remove or replace code covered by this backwards compatibility promise, it is
 first deprecated in the next minor release before being removed in the next major release.
 
 A code is marked as deprecated by adding a ``@deprecated`` PHPDoc to
diff --git a/docs/components_and_bundles/bundles/SyliusGridBundle/your_first_grid.rst b/docs/components_and_bundles/bundles/SyliusGridBundle/your_first_grid.rst
@@ -160,7 +160,7 @@ This first requires a :doc:`custom repository method </customization/repository>
 .. note::
 
     The repository method has to return a queryBuilder object, since the query has to adjustable depending on the filters and sorting the user later applies.
-    Furthermore, all sub entities you wish to use later for filtering have to be joined explicitely in the query.
+    Furthermore, all sub entities you wish to use later for filtering have to be joined explicitly in the query.
 
 Then you can set up your filter to accordingly:
 
diff --git a/docs/cookbook/emails/mailer.rst b/docs/cookbook/emails/mailer.rst
@@ -22,7 +22,7 @@ on by default, so there is nothing to worry about if you did not change anything
 
 .. warning::
 
-    Remember that the parameters like username or password must not be commited publicly to your repository.
+    Remember that the parameters like username or password must not be committed publicly to your repository.
     Save them as environment variables on your server.
 
 Learn More
diff --git a/docs/cookbook/frontend/google-analytics.rst b/docs/cookbook/frontend/google-analytics.rst
@@ -4,7 +4,7 @@ How to add Google Analytics script to shop?
 All shops tend to observe traffic on their websites, the most popular tool for that is Google Analytics.
 In Sylius we have two ways to enable it:
 
-*If you have the Sylius layout overriden completely then:*
+*If you have the Sylius layout overridden completely then:*
 
 * paste the script directly into :ref:`head section of the layout <google_analytics_to_head_section>`
 
diff --git a/docs/cookbook/images/images.rst b/docs/cookbook/images/images.rst
@@ -65,7 +65,7 @@ The ``imagine_filter('name')`` is a twig filter. This is how you would get an im
 How to add custom image resizing filters?
 -----------------------------------------
 
-If the filters we have in Sylius by deafult are not suitable for your needs, you can easily add your own.
+If the filters we have in Sylius by default are not suitable for your needs, you can easily add your own.
 
 All you need to do is to configure new filter in the ``config/packages/liip_imagine.yaml`` file.
 For example you can create a filter for advertisement banners:
