Explain the naming philosophy (#4265)
Explain the naming philosophy (#4265)

* Explain the naming philosophy

I don't know if this is the right place. But there should be a short introduction like this. Please make this section (i.e. anchor) the link target for codeception.com "User Centric Tests => Learn more"

Details:

* grab: Is there an easier exmple you can think of? One that doesn't require the Asserts Module?

* Missing in the list is "have" and maybe "expect". Maybe I can convince you to change those :-) See https://github.com/Codeception/Codeception/issues/4257

I'd like to rewrite the next section (Actors) too. Questions:

* I guess the term "Actor" is a leftover from previous versions of Codeception? More precise: Today, it's not really important (anymore) to know the term "Actor", is it?

* What do you mean by "Actor classes are not written but generated from suite configuration." => That they are *generated* automatically?

* Update 02-GettingStarted.md

See https://github.com/Codeception/Codeception/pull/4265#discussion_r119994046 and https://github.com/Codeception/Codeception/pull/4265#discussion_r119994055

* Update 02-GettingStarted.md

See https://github.com/Codeception/Codeception/pull/4265#pullrequestreview-41927106

Naktibalda/Codeception,Naktibalda/Codeception,tasselchof/Codeception,tasselchof/Codeception,Codeception/base,Codeception/base,Naktibalda/Codeception,Codeception/Codeception,Codeception/base,tasselchof/Codeception,Codeception/Codeception