Issues following the README.md when learning how to set things up

[cheuni02]

Issue 1) The readme line 267 says npx wdio . but this assumes thart wdio.config.js file is already created on the repo, but doesn't menation that the repo already has

• android-wdio.conf.js
• ios-wdio.conf.js

under /config

so perhaps add the line underneath it to run npx android-wdio or npx ios-wdio to save the user from running npx init wdio . first from line 202?

Issue 2) the current set of questions asked when running 'npm init wdio .' is now different to what is shown in the readme.

Expected questions in the readme from line 204 to 214:

2- Using the WDIO Configuration Helper select the options you want to select. In my case I decided to use:  
* On my local machine
* Mocha
* No compiler
* Spect Location: Default
* Do you want WebDriverIO to generate some test files?: No
* Reporter: Spec
* No Plugin 
* Service: Appium
* Base URL: Default
* NPM Install: Yes

Actual questions:

the questions now asked (after cloning this repo first) are:

i) A project named "webdriverio-tests" was detected at "/Users/<username>/<some more folders>/mocha-wdio-appium/exercises/appium-demo", correct? (i selected yes)
ii) What type of testing would you like to do? 

possible answers:
- E2E Testing - of Web or Mobile Applications **(i assume to pick this one?)**
- Component or Unit Testing - in the browser
    > https://webdriver.io/docs/component-testing 
- Desktop Testing - of Electron Applications
    > https://webdriver.io/docs/desktop-testing/electron 
- Desktop Testing - of MacOS Applications
    > https://webdriver.io/docs/desktop-testing/macos 
- VS Code Extension Testing
    > https://webdriver.io/docs/vscode-extension-testing 

iii) Where is your automation backend located? (selected 'on my local machine')
iv) Which environment you would like to automate?

possible answers:
- Web - web applications in the browser 
- Mobile - native, hybrid and mobile web apps, on Android or iOS **(i assume to pick this one?)**

v) Which mobile environment you'ld like to automate?

possible answers:
- Android - native, hybrid and mobile web apps, tested on emulators and real devices
    > using UiAutomator2 (https://www.npmjs.com/package/appium-uiautomator2-driver) **(i chose this one following the tutorial for now)** 
-   iOS - applications on iOS, iPadOS, and tvOS
    > using XCTest (https://appium.github.io/appium-xcuitest-driver) 

vi) Which framework do you want to use? **(selected Mocha (https://mochajs.org/) )**
vii) Do you want to use a compiler? **(selected "No")**
viii) Do you want WebdriverIO to autogenerate some test files? **(selected "No")**
ix) What should be the location of your spec files? **(gave '/appium-demo/test/specs/)**
x)  Do you want to use page objects (https://martinfowler.com/bliki/PageObject.html)?  **(selected "No")**
xi) Which reporter do you want to use? **(chose 'spec' as per the tutorial)**
xii) Do you want to add a plugin to your test setup? **(pressed 'enter' to select "No")**
xiii) Do you want to add a service to your test setup? **(selected "appium")**
xv) Do you want me to run `npm install`  **(selected "Yes")**

Wasn't sure which answers to pick and the resulting capabilities object generated in the wdio.conf.js doesn't look anything like the one in the tutorial

    capabilities: [{
        // capabilities for local Appium web tests on an Android Emulator
        platformName: 'Android',
        browserName: 'Chrome',
        'appium:deviceName': 'Android GoogleAPI Emulator',
        'appium:platformVersion': '12.0',
        'appium:automationName': 'UiAutomator2',
    }],

it won't have the property:
'appium:app':

and for some reason has the property:
browserName: 'Chrome',

when I didn't even specify this was browser testing (meant to be iOS or Android mobile app 😠)

Issue 3)
Typo at line 240

Expected:

• Set up the capabilities for iOS(Emulator sample)

Actual

• Set up the capabilities for Android(Emulator sample)