Update to 6 in STEP and README.md

Author: github-actions[bot]

.github/steps/-step.txt

@@ -1 +1 @@
-5
+6

README.md

@@ -16,45 +16,55 @@ _Create a release based workflow that is built on the foundations of the GitHub
 </header>
 
 <!--
- <<< Author notes: Step 5 >>>
+ <<< Author notes: Step 6 >>>
  Start this step by acknowledging the previous step.
  Define terms and link to docs.github.com.
 -->
 
-## Step 5: Finalize the release
+## Step 6: Commit a hotfix to the release
 
-_Awesome work on the release notes :+1:_
+_Almost there :heart:_
 
-### Finalizing releases
+Notice that I didn't delete the branch? That's intentional.
 
-It's important to be aware of the information what will be visible in that release. In the pre-release, the version and commit messages are visible.
+Sometimes mistakes can happen with releases, and we'll want to be able to correct them on the same branch.
 
-![image](https://user-images.githubusercontent.com/13326548/47883578-bdba7780-ddea-11e8-84b8-563e12f02ca6.png)
+Now that your release is finalized, we have a confession to make. Somewhere in our recent update, I made a mistake and introduced a bug. Instead of changing the text colors to green, we changed the whole game background.
 
-### Semantic versioning
+_Tip: Sometimes GitHub Pages takes a few minutes to update. Your page might not immediately show the recent updates you've made._
 
-Semantic versioning is a formal convention for specifying compatibility. It uses a three-part version number: **major version**; **minor version**; and **patch**. Version numbers convey meaning about the underlying code and what has been modified. For example, versioning could be handled as follows:
+![image](https://user-images.githubusercontent.com/13326548/48045461-487dd800-e145-11e8-843c-b91a82213eb8.png)
 
-| Code status | Stage | Rule | Example version |
-| ------------------------------- | ------------- | ---------------------------------------------------------------------- | --------------- |
-| First release | New product | Start with 1.0.0 | 1.0.0 |
-| Backward compatible fix | Patch release | Increment the third digit | 1.0.1 |
-| Backward compatible new feature | Minor release | Increment the middle digit and reset the last digit to zero | 1.1.0 |
-| Breaking updates | Major release | Increment the first digit and reset the middle and last digits to zero | 2.0.0 |
+"Hotfixes", or a quick fix to address a bug in software, are a normal part of development. Oftentimes you'll see application updates whose only description is "bug fixes".
 
-Check out this article on [Semantic versioning](https://semver.org/) to learn more.
+When bugs come up after you release a version, you'll need to address them. We've already created a `hotfix-v1.0.1` and `fix-game-background` branches for you to start.
 
-### Finalize the release
+We'll submit a hotfix by creating and merging the pull request.
 
-Now let's change our recently automated release from _draft_ to _latest release_.
+### :keyboard: Activity: Create and merge the hotfix pull request
 
-### :keyboard: Activity: Finalize release
+1. Open a pull request with `hotfix-v1.0.1` as the `base` branch, and `fix-game-background` as the `compare` branch.
+1. Fill in the pull request template to describe your changes. You can set the pull request title to "Hotfix for broken game style". You can include a detailed pull request body, an example is below:
+ ```
+ ## Description:
+ - Fixed bug, set game background back to black
+ ```
+1. Review the changes and click **Create pull request**.
+1. We want to merge this into our hotfix branch now so click **Merge pull request**.
 
-1. In a separate tab, go to the **Releases** page for this repository.
- - _Tip: To reach this page, click the **Code** tab at the top of your repository. Then, find the navigation bar below the repository description, and click the **Releases** heading link._
-1. Click the **Edit** button next to your draft release.
-1. Ensure the _Target_ branch is set to `main`.
-1. Click **Publish release**.
+Now we want these changes merged into `main` as well so let's create and merge a pull request with our hotfix to `main`.
+
+### :keyboard: Activity: Create the release pull request
+
+1. Open a pull request with `main` as the `base` branch, and `hotfix-v1.0.1` as the `compare` branch.
+1. Ensure the title of your pull request is "Hotfix v1.0.1".
+1. Include a detailed pull request body, an example is below:
+ ```
+ ## Description:
+ - Fixed bug introduced in last production release - set game background back to black
+ ```
+1. Review the changes and click **Create pull request**.
+1. Click **Merge pull request**.
 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.
 
 <footer>