Updated README.md steps to run

Author: ibarra-michelle

Diff for: README.md

@@ -23,8 +23,20 @@ application will attempt to infer sufficient/required properties from the
 target project and generate the best possible metadata for inclusion in the
 agency inventory.
 
-Using GitHub Actions to generate the code.json file
----------------
+Agency code.json daily update through GitHub Actions
+=========
+
+GitHub Actions is being used to run a scheduled event to create the Agency's code.json file daily.
+
+As mentioned earlier, if a "code.json" snippet file is not provided by the project maintainer, the
+application will attempt to infer sufficient/required properties from the
+target project and generate the best possible metadata for inclusion in the
+agency inventory.
+
+The example EPA Agency code.json for the github.com/USEPA organization can be [found here](https://github.com/USEPA/code-json-generator/tree/output). 
+
+### Generating the code.json file
+
 The code.json file can be generated by any of the GitHub Actions: 
 
 1. The [daily.yml](https://github.com/USEPA/code-json-generator/actions/workflows/daily.yml) generates the code.json file to this repository's [output branch](https://github.com/USEPA/code-json-generator/tree/output). This workflow is enabled.
@@ -33,20 +45,22 @@ The code.json file can be generated by any of the GitHub Actions:
 
 3. The [go-push (replacing Build and Deploy)](https://github.com/USEPA/code-json-generator/actions/workflows/go-push.yml) generates the code.json file to this repository's [master branch](https://github.com/USEPA/code-json-generator/tree/master) on the git push command. This workflow is disabled.
 
-Branch Directory
----------------
+### Branch Directory
+
 1. output - includes the code.json file generated by the [daily.yml](https://github.com/USEPA/code-json-generator/actions/workflows/daily.yml).
 2. cloudgov-deployment - provides intial code-json-generator GitHub Action workflow and removes 4000+ commit history generating the code.json file and deploying to cloud.gov. 
 3. including-history and history-cloud.gov-deployment - provides intial code-json-generator GitHub Action workflow and includes 4000+ commit history generating the code.json file and deploying to cloud.gov. 
 
 
-Getting Started - deploying to cloud.gov
----------------
+Getting Started
+=========
 
 This section describes the process to acquire and run the code-json-generator
-application in cloud.gov with the daily-deploy.yml workflow.
+application locally, GitHub, and in cloud.gov.
 
-### Prerequisites
+## Prerequisites
+
+Follow these prerequisites for running code.json generator locally, in GitHub, and for deploying to cloud.gov.
 
 This application is a command line Node application. Node must be installed
 on the system prior to running this application.
@@ -71,11 +85,9 @@ is provided to help get started.
 3. Move the new configuration file from the etc folder into the bin folder.
 4. Rename the configuration file to create-agency-inventory-config.js.
 
-Running locally or on cloud.gov
--------------------------------
-You can run the code.json generator locally or deploy it to cloud.gov.
 
-### Run the application locally
+## Run the application locally
+
 
 Running the application locally will help identify the specific repositories with missing or invalid code.json files. After all repositories have a valid code.json file, running the application will generate the Agency code.json locally.
 
@@ -107,9 +119,23 @@ $ create-inventory.js --configFile ./create-agency-inventory.config.json > code.
 > in the current working directory and is called `create-agency-inventory.config.json`.
 > Adjust this usage to suit actual work environment.
 
-Deployment to Cloud.gov with GitHub Actions
--------------------------------------------
-You can deploy the app to Cloud.gov with GitHub Actions.
+## Run with GitHub Actions
+
+
+To run the application with GitHub Actions, you need to:
+
+1. Change the working directory to the .github/workflows folder.
+
+2. Open the daily.yml file.
+
+3. Update the `schedule` event per the desired frequency.
+
+4. Save, commit and push your changes.
+
+
+## Deployment to Cloud.gov with GitHub Actions
+
+You can deploy the code.json generator to Cloud.gov with GitHub Actions.
 
 ### Prerequisites
 To do this you will need a Cloud.gov account and the [Cloud Foundry Command Line Tools](https://github.com/cloudfoundry/cli#installers-and-compressed-binaries) installed on your machine.  
@@ -134,7 +160,7 @@ You need to establish the name of your application before deploying it to cloud.
 
 5. You will see the code.json file located at: your-app-name.app.cloud.gov/code.json
 
-### Update frequency of the Agency's code.json file
+#### Update frequency of the Agency's code.json file
 
 You can modify how frequently the Agency's code.json file is generated and published to cloud.gov.
 
@@ -146,20 +172,8 @@ You can modify how frequently the Agency's code.json file is generated and publi
 
 4. Save, commit and push your changes.
 
-Agency code.json Daily update through GitHub Actions
--------------------------------------------
-
-GitHub Actions is being used to run a scheduled event to create the Agency's code.json file daily.
-
-As mentioned earlier, if a "code.json" snippet file is not provided by the project maintainer, the
-application will attempt to infer sufficient/required properties from the
-target project and generate the best possible metadata for inclusion in the
-agency inventory.
-
-The example EPA Agency code.json for the github.com/USEPA organization can be [found here](https://code-json-cg.app.cloud.gov/code.json). 
-
 Development
------------
+=========
 
 To develop and possibly contribute to this project please review the
 [code of conduct][4] and [contributing guidelines][5].