auto updated documentation

Author: DavertMik

changelog.markdown

@@ -7,6 +7,14 @@ title: Codeception Changelog
 
 # Changelog
 
+#### 2.2.12
+
+* Don't skip other tests after a failed test [#4226](https://github.com/Codeception/Codeception/issues/4226) by **[Naktibalda](https://github.com/Naktibalda)**
+* **[REST]** `seeResponseContainsJson` doesn't crash when json response is not an array by **[Naktibalda](https://github.com/Naktibalda)**
+* **[PhpBrowser]** Fixed redirecting to schemaless url by **[Naktibalda](https://github.com/Naktibalda)** [#4218](https://github.com/Codeception/Codeception/issues/4218)
+* **[Doctrine2]** Added `grabEntityFromRepository`, `grabEntitiesFromRepository` methods by **[maximelebastard](https://github.com/maximelebastard)**
+* **[REST]** Don't fail dontSee*JsonPath assertions when response is scalar value. Closes [#4237](https://github.com/Codeception/Codeception/issues/4237) by **[Naktibalda](https://github.com/Naktibalda)** 
+
 #### 2.2.11
 
 * **[WebDriver]** Added `_restart` method to restart browser with a new configuration. 

docs/01-Introduction.md

@@ -15,10 +15,10 @@ but with tests you can cover the most important parts of your app and at least b
 
 There are plenty of ways to test your application.
 The most popular paradigm is [Unit Testing](http://en.wikipedia.org/wiki/Unit_testing).
-For web applications, testing just the controller and / or the model doesn't prove that your application is working.
+For web applications, testing just the controller and/or the model doesn't prove that your application is working.
 To test the behavior of your application as a whole, you should write functional or acceptance tests.
 
-Codeception supports these testing types.
+Codeception supports all three testing types.
 Out of the box you have tools for writing unit, functional, and acceptance tests in a unified framework.
 
 Let's review the listed testing paradigms in reverse order.
@@ -27,7 +27,7 @@ Let's review the listed testing paradigms in reverse order.
 
 How does your client, manager, tester, or any other non-technical person know your website is working?
 By opening the browser, accessing a site, clicking on links, filling in the forms,
-and actually seeing the content on a web page. They has no idea of the framework, database, web-server,
+and actually seeing the content on a web page. They have no idea of the framework, database, web-server,
 or programming language you use or why the application did not behave as expected.
 
 Acceptance tests can cover standard but complex scenarios from a user's perspective.
@@ -148,9 +148,9 @@ not a pure unit test)
 
 ## Conclusion
 
-Despite the wide popularity of *TDD* (Test Driven Development), some PHP developers never write automated tests for their applications mostly because they think it's hard, slow or boring..
+Despite the wide popularity of *TDD* (Test Driven Development), some PHP developers never write automated tests for their applications mostly because they think it's hard, slow or boring.
 The Codeception framework was developed to actually make testing fun.
-It allows writing unit, functional, integration, and acceptance tests, in a single, coherent style.
+It allows writing unit, functional, integration, and acceptance tests in a single, coherent style.
 
 It can be called a *BDD* (Behavior Driven Development) framework. All Codeception tests are written in a descriptive manner.
 Just by looking at the test body, you can clearly understand what is being tested and how it is performed.

docs/02-GettingStarted.md

@@ -7,8 +7,8 @@ title: 02-GettingStarted - Codeception - Documentation
 
 Let's take a look at Codeception's architecture. We'll assume that you have already [installed](http://codeception.com/install) it
 and bootstrapped your first test suites. Codeception has generated three of them: unit, functional, and acceptance.
-They are well described in the previous chapter. Inside your __/tests__ folder you will have three config files and three directories
-with names corresponding to these suites. Suites are independent groups of tests with a common purpose.
+They are well described in the [previous chapter](http://codeception.com/docs/01-Introduction). Inside your __/tests__ folder you will have three `.yml` config files and three directories
+with names corresponding to these suites: `unit`, `functional`, `acceptance`. Suites are independent groups of tests with a common purpose.
 
 ## Actors
 
@@ -17,7 +17,7 @@ We have a UnitTester, who executes functions and tests the code. We also have a
 who tests the application as a whole, with knowledge of its internals. Lastly we have an AcceptanceTester, a user who works with our application
 through an interface that we provide.
 
-Actor classes are not written but generated from suite configuration. **Methods of actor classes are generally taken from Codeception Modules**.
+Actor classes are not written but generated from suite configuration. **Methods of actor classes are generally taken from [Codeception Modules](http://codeception.com/docs/06-ModulesAndHelpers)**.
 Each module provides predefined actions for different testing purposes, and they can be combined to fit the testing environment.
 Codeception tries to solve 90% of possible testing issues in its modules, so you don't have to reinvent the wheel.
 We think that you can spend more time on writing tests and less on writing support code to make those tests run.
@@ -65,21 +65,21 @@ and choosing a proper action from the auto-completion list. Let's log in to our
 {% highlight php %}
 
 <?php
-$I = new AcceptanceTester($scenario);
+$I = new AcceptanceTester($scenario); // actor class initialization
 $I->wantTo('login to website');
 
 
 {% endhighlight %}
 
-The `wantTo` section describes your scenario in brief. There are additional comment methods that are useful to describe context of a scenario:
+The `wantTo` section describes your scenario in brief. There are additional comment methods that are useful to describe the context of a scenario:
 
 {% highlight php %}
 
 <?php
 $I = new AcceptanceTester($scenario);
 $I->am('user'); // actor's role
 $I->wantTo('login to website'); // feature to test
-$I->lookForwardTo('access all website features'); // result to achieve
+$I->lookForwardTo('access website features for logged-in users'); // result to achieve
 
 {% endhighlight %}
 
@@ -94,7 +94,7 @@ Then we are sent to a user page, where we see the text `Hello, %username%`. Let'
 $I = new AcceptanceTester($scenario);
 $I->am('user');
 $I->wantTo('login to website');
-$I->lookForwardTo('access all website features');
+$I->lookForwardTo('access website features for logged-in users');
 $I->amOnPage('/login');
 $I->fillField('Username','davert');
 $I->fillField('Password','qwerty');
@@ -109,7 +109,7 @@ this test transforms into plain English text:
 {% highlight yaml %}
 I am user
 I wantTo login to website
-I lookForwardTo access all website features
+I lookForwardTo access website features for logged-in users
 I amOnPage '/login'
 I fillField 'Username','davert'
 I fillField 'Password','qwerty'
@@ -182,7 +182,7 @@ Signature: SigninCept.php
 Test: tests/acceptance/SigninCept.php
 Scenario --
  I am user
- I look forward to access all website features
+ I look forward to access website features for logged-in users
  I am on page "/login"
  I fill field "Username" "davert"
  I fill field "Password" "qwerty"
@@ -212,7 +212,7 @@ There is also a global bootstrap file located in the `tests` directory. It can b
 Codeception supports three test formats. Beside the previously described scenario-based Cept format,
 Codeception can also execute [PHPUnit test files for unit testing](http://codeception.com/docs/05-UnitTests), and Cest format.
 
-Cest combines scenario-driven test approach with OOP design. In case you want to group a few testing scenarios into one you should consider using Cest format.
+**Cest** combines scenario-driven test approach with OOP design. In case you want to group a few testing scenarios into one, you should consider using Cest format.
 In the example below we are testing CRUD actions within a single file but with several tests (one per operation):
 
 {% highlight php %}
@@ -321,7 +321,7 @@ php codecept run tests/acceptance/backend
 {% endhighlight %}
 
 Using regular expressions, you can even run many different test methods from the same directory or class.
-For example, this will execute all acceptance tests from the `backend` dir beginning with the word login:
+For example, this will execute all acceptance tests from the `backend` dir beginning with the word "login":
 
 {% highlight bash %}