removing step references

Author: mattdavis0351

responses/01_explain-environment.md

@@ -14,27 +14,6 @@ From 30,000 feet GitHub Actions is made up of the following components, with eac
 | Step                | A <b>step</b> is a set of tasks performed by a <b>job</b>.  <b>Steps</b> can run <b>commands</b> or <b>actions</b>.                                                                                                                                                                                               |
 | Virtual Environment | The <b>virtual environment</b> of a GitHub-hosted <b>runner</b> includes the virtual machine's hardware configuration, operating system, and installed software.                                                                                                                                                  |
 | Workflow            | A configurable automated process that you can set up in your repository.  <b>Workflows</b> are made up of one or more <b>jobs</b> and can be scheduled or activated by an <b>event</b>.                                                                                                                           |
-<!-- 
-Each component can be expanded for more information.
-
-<details><summary>Action</summary>
-Individual tasks that you combine as <b>steps</b> to create a <b>job</b>. <b>Actions</b> are the smallest portable building block of a workflow.  To use an <b>action</b> in a workflow, you <b>must include it as a step.</b></details>
-<details><summary>Artifact</summary>
-<b>Artifacts</b> are the files created when you build and test your code. <b>Artifacts</b> might include binary or package files, test results, screenshots, or log files.  <b>Artifacts</b> can be used by the other <b>jobs</b> in the workflow or deployed directly by the <b>workflow</b>.</details>
-<details><summary>Event</summary>
-A specific activity that triggers a <b>workflow</b> run.</details>
-<details><summary>Job</summary>
-A defined task made up of <b>steps</b>. Each <b>job</b> is run in a fresh instance of the <b>virtual environment</b>. <b>Jobs</b> can run at the same time in parallel or be dependent on the status of a previous <b>job</b> and run sequentially.</details>
-<details><summary>Runner</summary>
-Any machine with the GitHub Actions <b>runner</b> application installed. You can use a <b>runner</b> hosted by GitHub or host your own <b>runner</b>. A <b>runner</b> waits for available <b>jobs</b>. <b>Runners</b> run one <b>job</b> at a time reporting the progress, logs, and final result back to GitHub.</details>
-<details><summary>Step</summary>
-A <b>step</b> is a set of tasks performed by a <b>job</b>.  <b>Steps</b> can run <b>commands</b> or <b>actions</b>.
-</details>
-<details><summary>Virtual Environment</summary>
-The <b>virtual environment</b> of a GitHub-hosted <b>runner</b> includes the virtual machine's hardware configuration, operating system, and installed software.
-</details>
-<details><summary>Workflow</summary>
-A configurable automated process that you can set up in your repository.  <b>Workflows</b> are made up of one or more <b>jobs</b> and can be scheduled or activated by an <b>event</b>.</details> -->
 
 ### How these pieces fit together
 

responses/02_modify-workflow.md

@@ -1,14 +1,14 @@
-## Step 2: Edit the current workflow
+## Edit the current workflow
 
 Currently `my-workflow.yml` is not set up correctly for our use-case.  It worked great for allowing us to take a high-level look at workflows, but if we want to use our custom Actions there are some changes that we have to make to it.
 
 ### :keyboard: Activity: Modify my-workflow.yml to remove boilerplate steps
 
 1. [Edit]({{workflowFile}}) the `my-workflow.yml`.
-1. Change the `name:` property to `JS Actions`
-1. Rename the job from `build` to `action`
-1. Remove the two steps that run commands, but leave the step that runs the checkout action.
-1. Commit these file changes to this branch
+2. Change the `name:` property to `JS Actions`
+3. Rename the job from `build` to `action`
+4. Remove the two steps that run commands, but leave the step that runs the checkout action.
+5. Commit these file changes to this branch
 
 I'll respond in this pull request once you make these changes.
 

responses/welcome-issue.md

@@ -45,7 +45,7 @@ In other courses, you may have noticed that some behaviors take me longer to res
 
 If you aren't already familiar, it may be a good idea to go through the [Introduction to GitHub Learning Lab](https://lab.github.com/githubtraining/introduction-to-github).
 
-## Step 1: Preparing your repository
+## Preparing your repository
 
 Actions are enabled on your repository by default, but we still have to tell our repository to use them.  We do this by creating a **workflow** file in our repository.