Merge pull request #190 from soyuka/2.0

Fix trough through

Author: dunglas

core/getting-started.md

@@ -56,7 +56,7 @@ API Platform Core is able to automatically expose entities mapped as "API resour
 operations.
 To expose your entities, you can use Docblock annotations, XML and YAML configuration files.
 
-Here is an example of entities mapped using annotations which will be exposed trough a REST API:
+Here is an example of entities mapped using annotations which will be exposed through a REST API:
 
 ```php
 <?php
@@ -138,7 +138,7 @@ class Offer
 }
 ```
 
-It is the minimal configuration required to expose `Product` and `Offer` entities as JSON-LD documents trough an hypermedia
+It is the minimal configuration required to expose `Product` and `Offer` entities as JSON-LD documents through an hypermedia
 web API.
 
 If you are familiar with the Symfony ecosystem, you noticed that entity classes are also mapped with Doctrine ORM annotations

core/serialization-groups-and-relations.md

@@ -136,7 +136,7 @@ In the following JSON document, the relation from a book to an author is represe
 ### Normalization
 
 To improve the application's performance, it is sometimes necessary to avoid issuing extra HTTP requests. It is possible
-to embed related objects (or only some of their properties) directly in the parent response trough serialization groups.
+to embed related objects (or only some of their properties) directly in the parent response through serialization groups.
 By using the following serialization groups annotations (`@Groups`), a JSON representation of the author is embedded in
 the book response:
 
@@ -239,7 +239,7 @@ class Book
 
 The following rules apply when denormalizating embedded relations:
 
-* If a `@id` key is present in the embedded resource, the object corresponding to the given URI will be retrieved trough
+* If a `@id` key is present in the embedded resource, the object corresponding to the given URI will be retrieved through
 the data provider and any changes in the embedded relation will be applied to that object.
 * If no `@id` key exists, a new object will be created containing data provided in the embedded JSON document.
 

deployment/heroku.md

@@ -1,7 +1,7 @@
 # Deploying an API Platform App on Heroku
 
 [Heroku](http://heroku.com) is a popular, fast, scalable and reliable *Platform As A Service* (PaaS). As Heroku offers a
-free plan including database support trough [Heroku Postgres](https://www.heroku.com/postgres), it's
+free plan including database support through [Heroku Postgres](https://www.heroku.com/postgres), it's
 a very convenient way to experiment with the API Platform.
 
 The API Platform Heroku integration also supports MySQL databases provided by [the ClearDB add-on](https://addons.heroku.com/cleardb).

deployment/index.md

@@ -3,7 +3,7 @@
 As an API Platform application is basically a standard Symfony application, [all Symfony deployment cookbooks](http://symfony.com/doc/current/cookbook/deployment/index.html)
 apply.
 
-However, API Platform also provide facilities to deploy applications trough containers and Platforms as a Service (PaaS):
+However, API Platform also provide facilities to deploy applications through containers and Platforms as a Service (PaaS):
 
 * [Deploying an API Platform App on Heroku](heroku.md)
 * [Using API Platform with Docker](docker.md)

distribution/testing.md

@@ -21,7 +21,7 @@ the API without having to write a single line of PHP.
 Feature: Manage books and their reviews
   In order to manage books and their reviews
   As a client software developer
-  I need to be able to retrieve, create, update and delete them trough the API.
+  I need to be able to retrieve, create, update and delete them through the API.
 
   # the "@createSchema" annotation provided by API Platform creates a temporary SQLite database for testing the API
   @createSchema
@@ -162,10 +162,10 @@ Clear the cache of the `test` environment:
 
     $ docker-compose exec web bin/console cache:clear --env=test
 
-Then run: 
+Then run:
 
     $ docker-compose run --rm web vendor/bin/behat`.
-    
+
 Everything should be green now. Your Linked Data API is now specified and tested thanks to Behat!
 
 You may also be interested by those alternative testing tools (not included in the API Platform distribution):