make a consistent step 10

Author: hectorsector

config.yml

@@ -338,7 +338,7 @@ steps:
 
 # 10
 - title: Trigger your first step with a GitHub event
-  description: Trigger your first step with a GitHub event
+  description: Add a pull_request.opened event.
   event: pull_request.synchronize
   actions:
   - type: getFileContents

responses/07.0_add-trigger.md

@@ -3,7 +3,7 @@ Great! Your learner now has information about what they're expected to do in thi
 ### Events
 Every step in a course will be triggered by a GitHub Event. All possible events are documented in [Events Types & Payloads on the GitHub Developer Guide](https://developer.github.com/v3/activity/events/types/).
 
-## Step 8: Add an event
+## Step 10: Add an event
 Let's now find the `event` that will trigger the step. Because we want the learner to open a new Pull Request, the event we're looking for is [`pull_request`](https://developer.github.com/v3/activity/events/types/#pullrequestevent). Whenever this event occurs, information about the pull request is delivered to Learning Lab. However, if we just write `pull_request`, _any_ interaction with a pull request will cause this step to be triggered. We're specifically looking for the learner to _open a pull request_. We can filter the event to only opened pull requests by using `pull_request.opened` instead.
 
 ### :keyboard: Add an event