diff --git a/.github/steps/-step.txt b/.github/steps/-step.txt
index 1e8b314..62d8fe9 100644
--- a/.github/steps/-step.txt
+++ b/.github/steps/-step.txt
@@ -1 +1 @@
-6
+X
diff --git a/README.md b/README.md
index 05cce92..e669411 100644
--- a/README.md
+++ b/README.md
@@ -14,22 +14,32 @@ _Collaborate and work together on GitHub._
-## Step 6: Merge your pull request
+## Finish
-_Almost there! :heart:_
+_Congratulations friend, you've completed this course!_
-You can now [merge](https://docs.github.com/en/get-started/quickstart/github-glossary#merge) your pull request!
+
-### :keyboard: Activity: Merge your pull request
+As you continue working on GitHub, remember that high quality reviews improve your projects. If you are new to a repository, inquire about what review practices they have so you can hit the ground running.
-1. Click **Merge pull request**.
-1. Delete the branch `update-game` (optional).
-1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
+Here's a recap of all the tasks you've accomplished in your repository:
+
+- You learned how to assign pull requests for review.
+- You left a review on a pull request.
+- You suggested changes to a pull request.
+- You applied suggested changes to a pull request.
+
+### What's next?
+
+- Try adding a [`CODEOWNERS`](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners) file to your project to automatically assign reviewers to pull requests.
+- We'd love to hear what you thought of this course [in our discussion board](https://github.com/orgs/skills/discussions/categories/review-pull-requests).
+- [Take another GitHub Skills course](https://github.com/skills).
+- [Read the GitHub Getting Started docs](https://docs.github.com/en/get-started).
+- To find projects to contribute to, check out [GitHub Explore](https://github.com/explore).