use more consistent messages for what the bot is expecting

hectorsector · hectorsector · commit a47123bb4444 · 2019-04-16T07:28:00.000-04:00
diff --git a/responses/congratulations.md b/responses/congratulations.md
@@ -12,4 +12,6 @@ You are finished with this course. You can see a deployed version of our work to
     - If your organization is on GitHub.com, [fork it]({{ forkURL }}).
     - If your organization is on GitHub Enterprise Server, [transfer the repository](https://help.github.com/enterprise/2.2/admin/articles/moving-a-repository-from-github-com-to-github-enterprise)
 
+I won't monitor any further events in this repository.
+
 Your next steps are in the [Innersource learning path]({{ learningPathURL }}).
diff --git a/responses/discoverability-answer.md b/responses/discoverability-answer.md
@@ -11,4 +11,7 @@ Some suggestions to ensure your teammates can find your repository are:
 
 Discover more about how to make a repository discoverable by visiting the **Files Changed** tab. It's OK if you want to do this later, any resources we cover throughout the course will be available at the end. 
 
-Please merge this PR.
+Please merge this PR.
+
+<hr>
+<h3 align="center">I'll respond when you merge this pull request.</h3>
diff --git a/responses/discoverable.md b/responses/discoverable.md
@@ -6,4 +6,5 @@ What is this repository for?
 
 ![screenshot of a repository with no description, link, or and just a few folders: .github, .vscode, _appendix, _events, _includes, _layouts](https://user-images.githubusercontent.com/16547949/56039355-2430b380-5d02-11e9-999c-aa139a8146c2.png)
 
-I'll respond when I detect you've submitted a comment on this PR.
+<hr>
+<h3 align="center">I'll respond when I detect you comment on this pull request.</h3>
diff --git a/responses/metrics-answer.md b/responses/metrics-answer.md
@@ -8,4 +8,5 @@ Here are some other ideas for measuring how well you're doing:
 - PRs to implement suggested features
 - number of collaborators to a project outside of maintaining team
 
-I'll respond when you merge this PR. 
+<hr>
+<h3 align="center">I'll respond when you merge this pull request.</h3>
diff --git a/responses/metrics.md b/responses/metrics.md
@@ -4,4 +4,5 @@ Once you've implemented Innersource strategies, how do you know it's working?
 
 What might be some ways to measure the success of Innersource strategies?
 
-I'll respond when you submit a comment to this PR. 
+<hr>
+<h3 align="center">I'll respond when you comment on this pull request.</h3>
diff --git a/responses/projects-answer.md b/responses/projects-answer.md
@@ -4,4 +4,5 @@ Without a clear project management strategy, you might as well pick any issue.
 
 Being explicit about your project management tool, whether it's inside of GitHub or elsewhere, will help potential contributors figure out whether their contribution will be immediately beneficial or triaged. 
 
-I'll respond when you merge this PR. 
+<hr>
+<h3 align="center">I'll respond when you merge this pull request.</h3>
diff --git a/responses/projects.md b/responses/projects.md
@@ -12,4 +12,5 @@ Here's some open issues in this company project. You're eager to help with this
 - [ ] Issue 3: Add a new slide
 - [ ] Issue 2: Activity 1: Your first caption
 
-I'll respond when you check one of the boxes above. 
+<hr>
+<h3 align="center">I'll respond when you check one of the answers above.</h3>
diff --git a/responses/publish.md b/responses/publish.md
@@ -7,4 +7,7 @@ To publish:
 1. Scroll down to the section titled _GitHub Pages_
 1. Select **master branch** in the Source drop down.
 
-That's all! GitHub Pages will then deploy your site and repo its status back to me. I'll respond when I detect that GitHub pages has finished deploying your site. 
+That's all! GitHub Pages will then deploy your site and repo its status back to me. 
+
+<hr>
+<h3 align="center">I'll respond when I detect that GitHub Pages has finished deploying your site.</h3>
diff --git a/responses/repo-owner-answer.md b/responses/repo-owner-answer.md
@@ -15,4 +15,7 @@ Here are some recommendations based on some :sparkles: use of GitHub that we've
 - name your repositories in a meaningful manner, usually a simple project or application name will suffice
 </summary>
 
-Please merge this PR.
+Please merge this PR.
+
+<hr>
+<h3 align="center">I'll respond when you merge this pull request.</h3>
diff --git a/responses/repo-owner.md b/responses/repo-owner.md
@@ -7,4 +7,5 @@ Does a repository exist at https://github.com/githubtraining/training-manual?
 - [ ] True, there is a repository at the given URL.
 - [ ] False, no repository exists at the given URL.
 
-I'll respond when I detect you've checked one of the boxes above. 
+<hr>
+<h3 align="center">I'll respond when you check one of the boxes above.</h3>
diff --git a/responses/templates-answer.md b/responses/templates-answer.md
@@ -4,4 +4,7 @@ Every project _can_ have a different way to submit bug reports, so all the answe
 
 But, how could you know? With issue and pull request templates, you can take the mystery out of the equation and allow anyone across the organization to know the way each project prefers to receive issues and contributions.
 
-Please merge this PR.
+Please merge this PR.
+
+<hr>
+<h3 align="center">I'll respond when you merge this pull request.</h3>
diff --git a/responses/templates.md b/responses/templates.md
@@ -9,4 +9,5 @@ Here are four different ways you could submit a bug report. Which is the _right_
 - [ ] Open an internal support ticket
 - [ ] DM or email the maintainer
 
-I'll respond when you check one of the boxes above. 
+<hr>
+<h3 align="center">I'll respond when you check one of the boxes above.</h3>
diff --git a/responses/welcome.md b/responses/welcome.md
@@ -18,4 +18,5 @@ Innersource and open source are the same thing.
 - [ ] True
 - [ ] False
 
-I'll respond when you select one of the options above.
+<hr>
+<h3 align="center">I'll respond when you check one of the boxes above.</h3>
diff --git a/responses/workflows-answer.md b/responses/workflows-answer.md
@@ -8,4 +8,7 @@ This PR covers the basics, but here are some recommendations to help any contrib
 - if you haven't picked a workflow, use a common and well documented one that your contributors can easily search for
 - be explicit about your deployment and release strategy
 
-I'll respond when you merge this PR.
+Please merge this PR.
+
+<hr>
+<h3 align="center">I'll respond when you merge this pull request.</h3>
diff --git a/responses/workflows.md b/responses/workflows.md
@@ -1,4 +1,4 @@
-This PR covers a few common workflow that are likely in use within your organization.
+This PR covers a few common workflows that are likely in use within your organization.
 
 ### Challenge question
 
@@ -12,4 +12,5 @@ Suppose you'd like to contribute to the repository whose branches are pictured b
 - [ ] `green-colors`
 - [ ] `config-release-drafter`
 
-I'll respond when I detect you've checked one of the boxes above. 
+<hr>
+<h3 align="center">I'll respond when you check one of the boxes above.</h3>
