updated docs for guides

Author: DavertMik

_includes/extensions.md

@@ -68,7 +68,7 @@ extensions:
 
 [See Source](https://github.com/Codeception/Codeception/blob/5.0/ext/Recorder.php)
 
-Saves a screenshot of each step in acceptance tests and shows them as a slideshow on one HTML page (here's an [example](https://codeception.com/images/recorder.gif))
+Saves a screenshot of each step in acceptance tests and shows them as a slideshow on one HTML page (here's an [example](http://codeception.com/images/recorder.gif))
 Activated only for suites with WebDriver module enabled.
 
 The screenshots are saved to `tests/_output/record_*` directories, open `index.html` to see them as a slideshow.

changelog.markdown

@@ -29,7 +29,7 @@ $I->click('LOGIN');
 $I->see('Welcome, Davert!');
 ```
 
-**This scenario can be performed either by PhpBrowser or by a "real" browser through WebDriver**.
+**This scenario can be performed either by PhpBrowser or by a real browser through WebDriver**.
 
 | | PhpBrowser | WebDriver |
 | --- | --- | --- |
@@ -763,20 +763,6 @@ WebDriver module provides advanced methods for the browser session, however, the
 
 Those methods can be used to create custom commands like `$I->startBrowser()` or used in [before/after](https://codeception.com/docs/06-ModulesAndHelpers#Hooks) hooks.
 
-## Error Reporting
-
-By default Codeception uses the `E_ALL & ~E_STRICT & ~E_DEPRECATED` error reporting level.
-In acceptance tests you might want to change this level depending on your framework's error policy.
-The error reporting level can be set in the suite configuration file:
-
-```yaml
-actor: AcceptanceTester
-# ...
-error_level: E_ALL & ~E_STRICT & ~E_DEPRECATED
-```
-
-`error_level` can also be set globally in `codeception.yml` file. In order to do that, you need to specify `error_level` as a part of `settings`. For more information, see [Global Configuration](https://codeception.com/docs/reference/Configuration). Note that suite specific `error_level` value will override global value.
-
 ## Conclusion
 
 Writing acceptance tests with Codeception and PhpBrowser is a good start.

docs/03-AcceptanceTests.md

@@ -14,15 +14,17 @@ to "send" requests to your app. So there's no real HTTP request made, but rather
 [Request object](https://github.com/symfony/browser-kit/blob/master/Request.php) with the required properties is
 passed to your framework's (front-)controller.
 
-As a first step, you need to enable Codeception's module for your framework in `functional.suite.yml` (see below).
+As a first step, you need to enable Codeception's module for your framework in `Functional.suite.yml` (see below).
 
 All of Codeception's framework modules share the same interface, and thus your tests are not bound to any one of them.
 This is a sample functional test:
 
-{% highlight php %}
-
+```php
 <?php
-// LoginCest.php
+
+namespace Tests\Functional;
+
+use \Tests\Support\FunctionalTester;
 
 class LoginCest
 {
@@ -37,8 +39,7 @@ class LoginCest
         // $I->seeEmailIsSent(); // only for Symfony
     }
 }
-
-{% endhighlight %}
+```
 
 As you see, the syntax is the same for functional and acceptance tests.
 
@@ -69,104 +70,81 @@ Keep your memory clean, avoid memory leaks and clean global and static variables
 ## Enabling Framework Modules
 
 You have a functional testing suite in the `tests/functional` directory.
-To start, you need to include one of the framework modules in the suite configuration file: `tests/functional.suite.yml`.
+To start, you need to include one of the framework modules in the suite configuration file: `tests/Functional.suite.yml`.
 
 ### Symfony
 
 To perform Symfony integration you just need to include the Symfony module into your test suite. If you also use Doctrine2,
 don't forget to include it too. To make the Doctrine2 module connect using the `doctrine` service from Symfony,
 you should specify the Symfony module as a dependency for Doctrine2:
 
-{% highlight yaml %}
-
-# functional.suite.yml
+```yaml
+# Functional.suite.yml
 
 actor: FunctionalTester
 modules:
     enabled:
         - Symfony
         - Doctrine2:
             depends: Symfony # connect to Symfony
-
-{% endhighlight %}
+```
 
 By default this module will search for AppKernel in the `app` directory.
 
 The module uses the Symfony Profiler to provide additional information and assertions.
 
 [See the full reference](https://codeception.com/docs/modules/Symfony)
 
-### Laravel5
-
-The [Laravel5](https://codeception.com/docs/modules/Laravel5) module is included and requires no configuration:
+### Laravel
 
-{% highlight yaml %}
+The [Laravel](https://codeception.com/docs/modules/Laravel) module is included and requires no configuration:
 
-# functional.suite.yml
+```yaml
+# Functional.suite.yml
 
 actor: FunctionalTester
 modules:
     enabled:
-        - Laravel5
-
-{% endhighlight %}
+        - Laravel
+```
 
 ### Yii2
 
 Yii2 tests are included in [Basic](https://github.com/yiisoft/yii2-app-basic)
 and [Advanced](https://github.com/yiisoft/yii2-app-advanced) application templates. Follow the Yii2 guides to start.
 
-### Zend Framework 2
+### Laminas
 
-Use [the ZF2 module](https://codeception.com/docs/modules/ZF2) to run functional tests inside Zend Framework 2:
+[Laminas](https://codeception.com/docs/modules/Laminas) tests can be executed with enabling a corresponding module.
 
-{% highlight yaml %}
-
-# functional.suite.yml
+```yaml
+# Functional.suite.yml
 
 actor: FunctionalTester
 modules:
     enabled:
-        - ZF2
-
-{% endhighlight %}
-
-### Zend Expressive
-
-[Zend Expressive](https://codeception.com/docs/modules/ZendExpressive) tests can be executed with enabling a corresponding module.
-
-{% highlight yaml %}
-
-# functional.suite.yml
-
-actor: FunctionalTester
-modules:
-    enabled:
-        - ZendExpressive
-
-{% endhighlight %}
+        - Laminas
+```
 
 > See module reference to more configuration options
 
-### Phalcon 4
+### Phalcon 5
 
-The `Phalcon4` module requires creating a bootstrap file which returns an instance of `\Phalcon\Mvc\Application`.
-To start writing functional tests with Phalcon support you should enable the `Phalcon4` module
+The `Phalcon5` module requires creating a bootstrap file which returns an instance of `\Phalcon\Mvc\Application`.
+To start writing functional tests with Phalcon support you should enable the `Phalcon5` module
 and provide the path to this bootstrap file:
 
-{% highlight yaml %}
-
-# functional.suite.yml
+```yaml
+# Functional.suite.yml
 
 actor: FunctionalTester
 modules:
     enabled:
-        - Phalcon4:
+        - Phalcon5:
             bootstrap: 'app/config/bootstrap.php'
              cleanup: true
              savepoints: true
-
-{% endhighlight %}
+```
 
 [See the full reference](https://codeception.com/docs/modules/Phalcon4)
 
@@ -178,53 +156,41 @@ and the same engine.
 
 Therefore we can open a web page with `amOnPage` method:
 
-{% highlight php %}
-
-<?php
+```php
 $I->amOnPage('/login');
-
-{% endhighlight %}
+```
 
 We can click links to open web pages:
 
-{% highlight php %}
-
-<?php
+```php
 $I->click('Logout');
 // click link inside .nav element
 $I->click('Logout', '.nav');
 // click by CSS
 $I->click('a.logout');
 // click with strict locator
 $I->click(['class' => 'logout']);
-
-{% endhighlight %}
+```
 
 We can submit forms as well:
 
-{% highlight php %}
-
-<?php
+```php
 $I->submitForm('form#login', ['name' => 'john', 'password' => '123456']);
 // alternatively
 $I->fillField('#login input[name=name]', 'john');
 $I->fillField('#login input[name=password]', '123456');
 $I->click('Submit', '#login');
-
-{% endhighlight %}
+```
 
 And do assertions:
 
-{% highlight php %}
-
-<?php
+```php
 $I->see('Welcome, john');
 $I->see('Logged in successfully', '.notice');
 $I->seeCurrentUrlEquals('/profile/john');
+```
 
-{% endhighlight %}
-
-Framework modules also contain additional methods to access framework internals. For instance, Laravel5, Phalcon,
+Framework modules also contain additional methods to access framework internals. For instance, Laravel, Phalcon,
 and Yii2 modules have a `seeRecord` method which uses the ActiveRecord layer to check that a record exists in the database.
 
 Take a look at the complete reference for the module you are using. Most of its methods are common to all modules
@@ -233,10 +199,10 @@ but some of them are unique.
 You can also access framework globals inside a test or access the dependency injection container
 inside the `Helper\Functional` class:
 
-{% highlight php %}
-
+```php
 <?php
-namespace Helper;
+
+namespace Tests\Support\Helper;
 
 class Functional extends \Codeception\Module
 {
@@ -246,8 +212,7 @@ class Functional extends \Codeception\Module
         $service->doSomething();
     }
 }
-
-{% endhighlight %}
+```
 
 Also check all available *Public Properties* of the used modules to get full access to their data.
 
@@ -257,13 +222,11 @@ By default Codeception uses the `E_ALL & ~E_STRICT & ~E_DEPRECATED` error report
 In functional tests you might want to change this level depending on your framework's error policy.
 The error reporting level can be set in the suite configuration file:
 
-{% highlight yaml %}
-
+```yaml
 actor: FunctionalTester
 ...
 error_level: E_ALL & ~E_STRICT & ~E_DEPRECATED
-
-{% endhighlight %}
+```
 
 `error_level` can also be set globally in `codeception.yml` file. In order to do that, you need to specify `error_level` as a part of `settings`. For more information, see [Global Configuration](https://codeception.com/docs/reference/Configuration). Note that suite specific `error_level` value will override global value.