add: parent action readme. Fix: yaml snippet prettier in readme.

Author: rchougule

README.md

@@ -2,7 +2,8 @@
 
 This respository contains a library of GitHub Actions to help you integrate your test suite with the [BrowserStack](https://browserstack.com) device cloud. 
 
-You need a BrowserStack username and access-key to run your tests on the BrowserStack device cloud. You can [sign-up for free trial](https://www.browserstack.com/users/sign_up) if you do not have an existing account. 
+You need a BrowserStack username and access-key to run your tests on the BrowserStack device cloud. You can [sign-up for free trial](https://www.browserstack.com/users/sign_up) if you do not have an existing account.
+
 If you want to test your open source project on BrowserStack then [sign-up here](https://www.browserstack.com/open-source) for lifetime free access to all our products.
 
 ## Available Actions
@@ -25,7 +26,7 @@ As this is a library of Actions, invoking this Action will trigger the `setup-en
     build-name: BUILD_INFO
     project-name: REPO_NAME
 ```
-We recommend you to invoke individual Actions from this library separately. A sample of two Actions being invoked back to back is shown below. You can additionally refer to the individual `README` ([setup-env](./setup-env), [setup-local](./setup-local)) of the Actions to know more about how they work, the inputs they support and their usage examples.
+We recommend you to invoke the Actions individually depending on the use case. A sample workflow for the same is shown below. You can additionally refer to the individual `README` ([setup-env](./setup-env), [setup-local](./setup-local)) of the Actions to know more about how they work, the inputs they support and their usage examples.
 
 ## Sample Workflow with usage of both Actions
 The workflow example below would be useful when the web application to be tested is hosted on the GitHub Actions runner environment, i.e. not accessible from the public Internet.
@@ -52,9 +53,12 @@ jobs:
           local-testing: start
           local-identifier: random
 ```
-Post these setup steps where both the Actions have been used, you have to build and run your application web server on the same machine, in daemon mode and thereafter invoke your test scripts. Your test scripts should use the environment variables that have been set by [`setup-env` Action](./setup-env). For more detailed steps on how to integrate your test suite with BrowserStack on GitHub Actions, visit [BrowserStack Documentation](http://browserstack.com/docs/automate/selenium/github-actions) for the same.
 
-After you are done running your tests, invoke the `setup-local` Action again with `local-testing: stop` as an input:
+### Note
+---
+Post these steps, you will have to build and run your application web server on the same runner environment. Further, invoke your test scripts by utilizing the environment variables that have been set by actions. For more detailed steps on how to integrate your test suite with BrowserStack on GitHub Actions, visit [BrowserStack Documentation](http://browserstack.com/docs/automate/selenium/github-actions) for the same.
+
+After you are done running your tests, invoke the `setup-local` Action again with `local-testing: stop` as the input:
 ```yaml
       - name: 'BrowserStackLocal Stop'
         uses: 'browserstack/github-actions/setup-local@master'

setup-env/README.md

@@ -16,7 +16,7 @@ This action sets up the following environment variables in the runner environmen
 * This action does not have any prerequisites.
 
 ## Usage
-```
+```yaml
 - name: 'BrowserStack Env Setup'
   uses: 'browserstack/github-actions/setup-env@master'
   with:
@@ -28,7 +28,7 @@ This action sets up the following environment variables in the runner environmen
 
 or
 
-```
+```yaml
 - name: 'BrowserStack Env Setup'
   uses: 'browserstack/github-actions/setup-env@master'
   with:

setup-local/README.md

@@ -39,7 +39,7 @@ The **browserstack/github-actions/setup-env@master** action should have been inv
 
 ## Usage
 Use the code snippet below in your workflow to start the BrowserStackLocal binary and establish the tunnel connection:
-```
+```yaml
 - name: 'Start BrowserStackLocal Tunnel'
   uses: 'browserstack/github-actions/setup-local@master'
   with:
@@ -49,7 +49,7 @@ Use the code snippet below in your workflow to start the BrowserStackLocal binar
 ```
 
 Use the code snippet below at the end of your workflow after the tests have completed. This will stop the BrowserStackLocal binary and upload the local binary logs (if any):
-```
+```yaml
 - name: 'Stop BrowserStackLocal'
   uses: 'browserstack/github-actions/setup-local@master'
   with: