Update to 5 in STEP and README.md

.github/steps/-step.txt

@@ -1 +1 @@
-4
+5

README.md

@@ -6,18 +6,23 @@ _Create and run a GitHub Actions workflow._
 
 </header>
 
-## Step 4: Merge your workflow file
+## Step 5: Trigger the workflow
 
-_You're now able to write and run an Actions workflow! :sparkles:_
+_You've now added a fully functioning workflow to your repository! :smile:_
 
-Merge your changes so the action will be a part of the `main` branch.
+The shell script in the workflow will run whenever a new pull request is opened.
 
-### :keyboard: Activity: Merge your workflow file
+**Seeing your _action_ in action**: The status of each workflow run that's triggered is shown in the pull request before it's merged: look for **All checks have passed** when you try out the steps below. You can also see a list of all the workflows that are running, or have finished running, in the **Actions** tab of your repository. From there, you can click on each workflow run to view more details and access log files.
 
-1. In your repo, click on the **Pull requests** tab.
-1. Click on the pull request you created in step 1.
-1. Click **Merge pull request**, then click **Confirm merge**.
-1. Optionally, click **Delete branch** to delete your `welcome-workflow` branch.
+![A screenshot of the Actions tab showing a list of workflow runs.](https://user-images.githubusercontent.com/16547949/62388049-4e64e600-b52a-11e9-8bf5-db0c5452360f.png)
+
+### :keyboard: Activity: Trigger the workflow
+
+1. Make a new branch named `test-workflow`.
+1. Make a change, such as adding an emoji to your README.md file, and commit the change directly to your new branch.
+1. In the **Pull requests** tab, create a pull request that will merge `test-workflow` into `main`.
+1. Watch the workflow running in the checks section of the pull request.
+1. Notice the comment that the workflow adds to the pull request.
 1. Wait about 20 seconds, then refresh this page (the one you're following instructions from). Another workflow will run and will replace the contents of this README file with instructions for the next step.
 
 <footer>