Bumped version

CHANGELOG.md

@@ -1,4 +1,14 @@
-## 0.7.0 - unreleased
+## 0.8.0 - unreleased
+
+ADDED:
+
+CHANGED:
+
+REMOVED:
+
+FIXED:
+
+## 0.7.0 - 2015-10-04
 
 ADDED:
 - A separate responder class
@@ -11,7 +21,7 @@ CHANGED:
 - JSON API exceptions extend `JsonApiException` thus they can be catched easier
 - Documents are moved to `JsonApi\Document` namespace from `JsonApi\Transfomer`
 - Refactored transformation to fix inclusion of multiple identical resource objects
-- When the data member is missing from the top source, the approriate exception is thrown
+- When the data member is missing from the top source, the appropriate exception is thrown
 
 REMOVED:
 - Different types of responses (e.g.: `FetchResponse`)

README.md

@@ -643,15 +643,15 @@ try {
 ```
 
 where `$response` is the instance of `Psr\Http\Message\ResponseInterface` and `sendResponse()` is a hypothetical
-function which sends the response received by its argument.
+function which sends the response received in its argument.
 
 To guarantee total customizability, we introduced the concept of __Exception Factories__. These are classes
 which can create all the exceptions thrown by Woohoo Labs. Yin. As an Exception Factory of your own choice is passed to
 every transformer and hydrator, you can completely customize what kind of exceptions you want to raise.
 
 The default [Exception Factory](src/JsonApi/Exception/ExceptionFactory) creates children
 of [`JsonApiException`-s](src/JsonApi/Exception) but you are free to create any type of exceptions (even the
-basic `\Exception` instances). When you want to customize the error document or the error objects of a
+basic `\Exception` instances). If you only want to customize the error document or the error objects of a
 `JsonApiException`, just extend it and override their `createErrorDocument()` or `getErrors()` method.
 
 #### `JsonApi` class