Merge pull request Codeception#69 from toniperic/patch-1

DavertMik · DavertMik · commit 5f38a0f3f81f · 2016-04-15T00:29:36.000+03:00
Update 02-GettingStarted.md
diff --git a/docs/02-GettingStarted.md b/docs/02-GettingStarted.md
@@ -11,7 +11,7 @@ Let's take a look at Codeception's architecture. We assume that you already [ins
 
 One of the main concepts of Codeception is representation of tests as actions of a person. We have a UnitTester, who executes functions and tests the code. We also have a FunctionalTester, a qualified tester, who tests the application as a whole, with knowledge of its internals. And an AcceptanceTester, a user that 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**. 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 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. By default AcceptanceTester relies on PhpBrowser module, which is set in `tests/acceptance.suite.yml` configuration file:
+Actor classes are not written but generated from suite configuration. **Methods of actor classes are generally taken from Codeception Modules**. 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. By default AcceptanceTester relies on PhpBrowser module, which is set in `tests/acceptance.suite.yml` configuration file:
 
 {% highlight yaml %}
 
@@ -312,4 +312,4 @@ We took a look into the Codeception structure. Most of the things you need were
 
 
 * **Next Chapter: [AcceptanceTests >](/docs/03-AcceptanceTests)**
-* **Previous Chapter: [< Introduction](/docs/01-Introduction)**
+* **Previous Chapter: [< Introduction](/docs/01-Introduction)**
