diff --git a/.github/steps/-step.txt b/.github/steps/-step.txt
index 00750ed..62d8fe9 100644
--- a/.github/steps/-step.txt
+++ b/.github/steps/-step.txt
@@ -1 +1 @@
-3
+X
diff --git a/README.md b/README.md
index e947237..0a6b370 100644
--- a/README.md
+++ b/README.md
@@ -14,44 +14,35 @@ _Useful tips when navigating through your repository._
-## Step 3: Fix a broken sidebar
+## Finish
-_Great job finding that commit :heart:_
+_Congratulations friend, you've completed this course! :tada:_
-Thanks for finding that commit! We now know that the sidebar was indeed added, and it was done in that commit. Let's see if we can dig a little deeper to find out if any planning or conversation, using comments, occurred around this change.
+
-As we've already seen, conversations in issues and pull requests can reference other work, but the amount of context goes much further than crosslinks. Remember, Git is version control! For example, the commit that you found in the last step is connected with much more information such as:
+In this course, you've learned a lot about finding and sharing information. Within a GitHub repository, you can find history about what changes were made, and more importantly, _why_ changes were made.
-- Who made the commit.
-- What other changes were included.
-- When the commit was made.
-- Which pull request the commit was a part of.
+### What's next?
-The pull request is important because it goes beyond knowing when a commit happened. You can know _why_ a commit happened. Finding history is not about _blaming_ anyone, but about seeing the bigger picture. Why were decisions made? Who was involved? What were the build outputs and test results for each commit? Who requested changes, and who approved them?
+You can enable GitHub Pages and see `docs/index.html` as a website!
-### Finding a pull request from a commit
+1. Replace `USERNAME` with your GitHub username and `REPONAME` with your GitHub repository name in `docs/index.html`.
+1. Under your repository name at the upper right, click :gear: **Settings**.
+1. Then on the lower left, click **Pages**.
+1. In the **GitHub Pages** section, select `main` in the **Select branch** drop-down menu and `/docs` in the **Select folder** drop-down menu.
+1. Click the **Save** button.
+1. Wait about 30 seconds then refresh the page. When you see "Your site is published at ...," you can click on the link to see your published site.
-When you're looking at a commit on GitHub, you can see a lot of information. From this view, you can also find a link to the pull request in which the commit was created. We'll use this in the next step.
+Check out these resources to learn more or get involved:
-
-
-### :keyboard: Activity: Fix a broken sidebar
-
-1. In the main branch [Edit the `docs/_sidebar.md` file](/docs/_sidebar.md).
-2. Correct the spelling of the reference `(doc-references__.md)` on line 4 by changing it into `(doc-references.md)`.
-3. Select or create a new branch `fix-sidebar` for this commit and start a pull request.
-4. Make sure that **main** is selected for **base:** and **fix-sidebar** for **compare:**.
-5. Using the **Assignees** section on the right side, assign yourself to the pull request.
-6. In the PR comment add 'Closes #2' and autolink issue #2.
-7. Click **Create pull request** and wait about 20 seconds.
-8. Merge this pull request.
-9. Delete the branch 'fix-sidebar'.
-10. 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.
+- Are you a student? Check out the [Student Developer Pack](https://education.github.com/pack).
+- [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).