From 3a67f1b19b536d87ea67980e635e5166e7cf5b13 Mon Sep 17 00:00:00 2001
From: github-actions <github-actions@github.com>
Date: Sun, 29 Oct 2023 20:56:00 +0000
Subject: [PATCH 1/8] Update game over message

---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 2485e1a..26641e4 100644
--- a/index.html
+++ b/index.html
@@ -47,7 +47,7 @@ <h1>Tic Tac Toe</h1>
   </tr>
 </table>
 
-<h2 hidden>Game over</h2>
+<h2 hidden>Game over, refresh to play again 🧑‍💻 🤖!</h2>
 
 <script>
   // Initialization

From d4570c269aa4238deca55aa568fcb2b62d16635e Mon Sep 17 00:00:00 2001
From: github-actions <github-actions@github.com>
Date: Sun, 29 Oct 2023 20:56:00 +0000
Subject: [PATCH 2/8] Update to 1 in STEP and README.md

---
 .github/steps/-step.txt |  2 +-
 README.md               | 57 ++++++++++++++---------------------------
 2 files changed, 20 insertions(+), 39 deletions(-)

diff --git a/.github/steps/-step.txt b/.github/steps/-step.txt
index 573541a..d00491f 100644
--- a/.github/steps/-step.txt
+++ b/.github/steps/-step.txt
@@ -1 +1 @@
-0
+1
diff --git a/README.md b/README.md
index 4ea4ec5..a710e36 100644
--- a/README.md
+++ b/README.md
@@ -14,51 +14,32 @@ _Collaborate and work together on GitHub._
 </header>
 
 <!--
-  <<< Author notes: Course start >>>
-  Include start button, a note about Actions minutes,
-  and tell the learner why they should take the course.
+  <<< Author notes: Step 1 >>>
+  Choose 3-5 steps for your course.
+  The first step is always the hardest, so pick something easy!
+  Link to docs.github.com for further explanations.
+  Encourage users to open new tabs for steps!
 -->
 
-## Welcome
+## Step 1: Open a pull request
 
-All great projects start with collaboration. Pull requests are the foundation of teamwork on GitHub — and pull request reviews give you the ability to work together and discuss changes specific to a pull request by commenting, requesting changes, or approving.
+_Welcome to "Review pull requests"! :wave:_
 
-- **Who is this for**: Developers, new GitHub users, users new to Git, students, managers, teams.
-- **What you'll learn**: When and how to request a review; how to provide a review of someone else's pull request.
-- **What you'll build**: We'll be reviewing a pull request for a simple game.
-- **Prerequisites**: We assume you are familiar with creating branches, commits, and pull requests—you can learn this in our [Introduction to GitHub](https://github.com/skills/introduction-to-github) course.
-- **How long**: This course takes less than 30 minutes to complete.
+Let's get started by opening a pull request.
 
-In this course, you will:
+**What is a pull request?**: Collaboration happens on a pull request. The pull request shows the changes in your branch to other people. This pull request is going to keep the changes you just made on your branch and propose applying them to the `main` branch.
 
-1. Open a pull request
-2. Assign yourself
-3. Leave a review
-4. Suggest changes
-5. Apply changes
-6. Merge your pull request
+### :keyboard: Activity: Create a pull request
 
-### How to start this course
-
-<!-- For start course, run in JavaScript:
-'https://github.com/new?' + new URLSearchParams({
-  template_owner: 'skills',
-  template_name: 'review-pull-requests',
-  owner: '@me',
-  name: 'skills-review-pull-requests',
-  description: 'My clone repository',
-  visibility: 'public',
-}).toString()
--->
-
-[![start-course](https://user-images.githubusercontent.com/1221423/235727646-4a590299-ffe5-480d-8cd5-8194ea184546.svg)](https://github.com/new?template_owner=skills&template_name=review-pull-requests&owner=%40me&name=skills-review-pull-requests&description=My+clone+repository&visibility=public)
-
-1. Right-click **Start course** and open the link in a new tab.
-2. In the new tab, most of the prompts will automatically fill in for you.
-   - For owner, choose your personal account or an organization to host the repository.
-   - We recommend creating a public repository, as private repositories will [use Actions minutes](https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions).
-   - Scroll down and click the **Create repository** button at the bottom of the form.
-3. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README.
+1. Click on the **Pull requests** tab in your repository.
+2. Click **New pull request**.
+3. In the **base:** dropdown, make sure **main** is selected.
+4. Select the **compare:** dropdown, and click `update-game`.
+5. Click **Create pull request**.
+6. Enter a title for your pull request: `Update the game over message`.
+7. Enter a description for your pull request: `Update the game over message so people know how to play again!`
+8. Click **Create pull request**.
+9. 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>
 

From ce523c8900fc117afaa780ad382158cd31d5f190 Mon Sep 17 00:00:00 2001
From: github-actions <github-actions@github.com>
Date: Sun, 29 Oct 2023 21:48:31 +0000
Subject: [PATCH 3/8] Update to 2 in STEP and README.md

---
 .github/steps/-step.txt |  2 +-
 README.md               | 34 +++++++++++++++-------------------
 2 files changed, 16 insertions(+), 20 deletions(-)

diff --git a/.github/steps/-step.txt b/.github/steps/-step.txt
index d00491f..0cfbf08 100644
--- a/.github/steps/-step.txt
+++ b/.github/steps/-step.txt
@@ -1 +1 @@
-1
+2
diff --git a/README.md b/README.md
index a710e36..7568d4c 100644
--- a/README.md
+++ b/README.md
@@ -14,32 +14,28 @@ _Collaborate and work together on GitHub._
 </header>
 
 <!--
-  <<< Author notes: Step 1 >>>
-  Choose 3-5 steps for your course.
-  The first step is always the hardest, so pick something easy!
-  Link to docs.github.com for further explanations.
-  Encourage users to open new tabs for steps!
+  <<< Author notes: Step 2 >>>
+  Start this step by acknowledging the previous step.
+  Define terms and link to docs.github.com.
+  Historic note: this step combines the commend, approve, and needs changes steps from the previous version.
 -->
 
-## Step 1: Open a pull request
+## Step 2: Assign yourself
 
-_Welcome to "Review pull requests"! :wave:_
+_Great job opening that pull request! :wave:_
 
-Let's get started by opening a pull request.
+**What is a _pull request review_?**: Reviewing a pull request is an opportunity to examine another contributor's changes and give them feedback. It's an awesome opportunity to learn more about how the project works and how others solve problems.
 
-**What is a pull request?**: Collaboration happens on a pull request. The pull request shows the changes in your branch to other people. This pull request is going to keep the changes you just made on your branch and propose applying them to the `main` branch.
+The best way to get a review is to ask for one. On GitHub, you can ask someone to review a pull request by assigning them as a reviewer or assignee. If you are not ready for review, consider [creating a draft pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) instead.
 
-### :keyboard: Activity: Create a pull request
+### :keyboard: Activity: Assign yourself
 
-1. Click on the **Pull requests** tab in your repository.
-2. Click **New pull request**.
-3. In the **base:** dropdown, make sure **main** is selected.
-4. Select the **compare:** dropdown, and click `update-game`.
-5. Click **Create pull request**.
-6. Enter a title for your pull request: `Update the game over message`.
-7. Enter a description for your pull request: `Update the game over message so people know how to play again!`
-8. Click **Create pull request**.
-9. 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.
+1. Open the pull request you just created.
+1. Under **Assignees** on the right side of the screen, add yourself.
+
+   Because you created the pull request, you can't assign yourself as a reviewer, but feel free to assign a friend as a reviewer instead to see how it works :smile:
+
+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>
 

From d218a45090d40292352d8251754f7278ae4065a5 Mon Sep 17 00:00:00 2001
From: github-actions <github-actions@github.com>
Date: Sun, 29 Oct 2023 21:51:14 +0000
Subject: [PATCH 4/8] Update to 3 in STEP and README.md

---
 .github/steps/-step.txt |  2 +-
 README.md               | 35 ++++++++++++++++++++++++++---------
 2 files changed, 27 insertions(+), 10 deletions(-)

diff --git a/.github/steps/-step.txt b/.github/steps/-step.txt
index 0cfbf08..00750ed 100644
--- a/.github/steps/-step.txt
+++ b/.github/steps/-step.txt
@@ -1 +1 @@
-2
+3
diff --git a/README.md b/README.md
index 7568d4c..328e389 100644
--- a/README.md
+++ b/README.md
@@ -14,27 +14,44 @@ _Collaborate and work together on GitHub._
 </header>
 
 <!--
-  <<< Author notes: Step 2 >>>
+  <<< Author notes: Step 3 >>>
   Start this step by acknowledging the previous step.
   Define terms and link to docs.github.com.
   Historic note: this step combines the commend, approve, and needs changes steps from the previous version.
 -->
 
-## Step 2: Assign yourself
+## Step 3: Leave a review
 
-_Great job opening that pull request! :wave:_
+_You assigned yourself! :tada:_
 
-**What is a _pull request review_?**: Reviewing a pull request is an opportunity to examine another contributor's changes and give them feedback. It's an awesome opportunity to learn more about how the project works and how others solve problems.
+Pull request reviews ensure quality and maintain momentum of changes to your project.
 
-The best way to get a review is to ask for one. On GitHub, you can ask someone to review a pull request by assigning them as a reviewer or assignee. If you are not ready for review, consider [creating a draft pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) instead.
+#### When reviewing a pull request:
 
-### :keyboard: Activity: Assign yourself
+1. Review the _title_ and _body_ of the pull request, and possibly any associated issue, to understand the intended change.
+1. Review the [diff](https://docs.github.com/en/get-started/quickstart/github-glossary#diff), the comparison of the proposed code, in the context of the whole project.
+1. For most things, try out the proposed change. Check if the actual change matches the intention. Find the repository's [contributing guide](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors) to find out how to review the changes.
 
-1. Open the pull request you just created.
-1. Under **Assignees** on the right side of the screen, add yourself.
+#### In your review comments:
 
-   Because you created the pull request, you can't assign yourself as a reviewer, but feel free to assign a friend as a reviewer instead to see how it works :smile:
+- Identify potential issues, risks, and limitations.
+- Suggest changes and improvements.
+- Share awareness of upcoming changes that the pull request doesn't account for.
+- Ask questions to verify shared understanding.
+- Highlight what the author did well and should keep doing.
+- Prioritize the most important feedback.
+- Be concise _and_ provide meaningful detail.
+- Treat the pull request author with kindness and empathy.
 
+When an approval or request for changes is not yet needed, consider using **comments**. An **approval** lets the author know you believe the pull request is safe to merge. **Requesting changes** lets the author know you believe the pull request is not ready to merge.
+
+### :keyboard: Activity: Leave a review
+
+1. On the pull request, click **Files changed**.
+1. Click **Review changes**.
+1. Add a comment with your initial thoughts on the pull request.
+1. Select _comment_. You won't be able to _approve_ or _request changes_ to your own pull request.
+1. Click **Submit review**.
 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>

From e03e3115753dd1d35daf917cb487f3763c95dd07 Mon Sep 17 00:00:00 2001
From: github-actions <github-actions@github.com>
Date: Sun, 29 Oct 2023 21:54:33 +0000
Subject: [PATCH 5/8] Update to 4 in STEP and README.md

---
 .github/steps/-step.txt |  2 +-
 README.md               | 41 +++++++++++++----------------------------
 2 files changed, 14 insertions(+), 29 deletions(-)

diff --git a/.github/steps/-step.txt b/.github/steps/-step.txt
index 00750ed..b8626c4 100644
--- a/.github/steps/-step.txt
+++ b/.github/steps/-step.txt
@@ -1 +1 @@
-3
+4
diff --git a/README.md b/README.md
index 328e389..72fa969 100644
--- a/README.md
+++ b/README.md
@@ -14,44 +14,29 @@ _Collaborate and work together on GitHub._
 </header>
 
 <!--
-  <<< Author notes: Step 3 >>>
+  <<< Author notes: Step 4 >>>
   Start this step by acknowledging the previous step.
   Define terms and link to docs.github.com.
-  Historic note: this step combines the commend, approve, and needs changes steps from the previous version.
 -->
 
-## Step 3: Leave a review
+## Step 4: Suggest changes
 
-_You assigned yourself! :tada:_
+_Nice work reviewing that pull request :sparkles:_
 
-Pull request reviews ensure quality and maintain momentum of changes to your project.
+Now that you have explored the different ways you can review a pull request it is time to learn how to use _suggest changes_.
 
-#### When reviewing a pull request:
+**What is _suggest changes_?**: This feature enables you to recommend a change to a pull request that the author can commit with the push of a button.
 
-1. Review the _title_ and _body_ of the pull request, and possibly any associated issue, to understand the intended change.
-1. Review the [diff](https://docs.github.com/en/get-started/quickstart/github-glossary#diff), the comparison of the proposed code, in the context of the whole project.
-1. For most things, try out the proposed change. Check if the actual change matches the intention. Find the repository's [contributing guide](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors) to find out how to review the changes.
-
-#### In your review comments:
-
-- Identify potential issues, risks, and limitations.
-- Suggest changes and improvements.
-- Share awareness of upcoming changes that the pull request doesn't account for.
-- Ask questions to verify shared understanding.
-- Highlight what the author did well and should keep doing.
-- Prioritize the most important feedback.
-- Be concise _and_ provide meaningful detail.
-- Treat the pull request author with kindness and empathy.
-
-When an approval or request for changes is not yet needed, consider using **comments**. An **approval** lets the author know you believe the pull request is safe to merge. **Requesting changes** lets the author know you believe the pull request is not ready to merge.
-
-### :keyboard: Activity: Leave a review
+### :keyboard: Activity: Suggest changes
 
 1. On the pull request, click **Files changed**.
-1. Click **Review changes**.
-1. Add a comment with your initial thoughts on the pull request.
-1. Select _comment_. You won't be able to _approve_ or _request changes_ to your own pull request.
-1. Click **Submit review**.
+1. Find the `index.html` changes.
+1. Hover your cursor next to the line numbers on the left side of the page.
+1. Click the blue plus icon.
+1. After the comment form appears, click the **Add a suggestion** button. <br>
+   ![add-a-suggestion-button](https://user-images.githubusercontent.com/97056108/184449714-61e8ee51-824a-48c1-9436-2dfd67f2c070.png)
+1. Edit the suggestion.
+1. Click **Add a single comment**.
 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>

From 247e5f9c360f09419726eb8b90a2a395d2aa12af Mon Sep 17 00:00:00 2001
From: github-actions <github-actions@github.com>
Date: Sun, 29 Oct 2023 22:02:00 +0000
Subject: [PATCH 6/8] Update to 5 in STEP and README.md

---
 .github/steps/-step.txt |  2 +-
 README.md               | 23 ++++++++---------------
 2 files changed, 9 insertions(+), 16 deletions(-)

diff --git a/.github/steps/-step.txt b/.github/steps/-step.txt
index b8626c4..7ed6ff8 100644
--- a/.github/steps/-step.txt
+++ b/.github/steps/-step.txt
@@ -1 +1 @@
-4
+5
diff --git a/README.md b/README.md
index 72fa969..c404a6d 100644
--- a/README.md
+++ b/README.md
@@ -14,29 +14,22 @@ _Collaborate and work together on GitHub._
 </header>
 
 <!--
-  <<< Author notes: Step 4 >>>
+  <<< Author notes: Step 5 >>>
   Start this step by acknowledging the previous step.
   Define terms and link to docs.github.com.
 -->
 
-## Step 4: Suggest changes
+## Step 5: Apply suggested changes
 
-_Nice work reviewing that pull request :sparkles:_
+_Nicely done suggesting changes! :partying_face:_
 
-Now that you have explored the different ways you can review a pull request it is time to learn how to use _suggest changes_.
+Now let's see how easy it is to [apply your suggestion](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request).
 
-**What is _suggest changes_?**: This feature enables you to recommend a change to a pull request that the author can commit with the push of a button.
+### :keyboard: Activity: Apply suggested changes
 
-### :keyboard: Activity: Suggest changes
-
-1. On the pull request, click **Files changed**.
-1. Find the `index.html` changes.
-1. Hover your cursor next to the line numbers on the left side of the page.
-1. Click the blue plus icon.
-1. After the comment form appears, click the **Add a suggestion** button. <br>
-   ![add-a-suggestion-button](https://user-images.githubusercontent.com/97056108/184449714-61e8ee51-824a-48c1-9436-2dfd67f2c070.png)
-1. Edit the suggestion.
-1. Click **Add a single comment**.
+1. Click **Commit suggestion**.
+1. Type a commit message.
+1. Click **Commit changes**.
 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>

From 450451af5f62a2ea0f273ffedbb0c31156fa377b Mon Sep 17 00:00:00 2001
From: Raphael Laucene <40581808+Raphaellaucene@users.noreply.github.com>
Date: Sat, 2 Mar 2024 11:04:01 -0300
Subject: [PATCH 7/8] Update index.html

change in game over message
---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 26641e4..cd45abe 100644
--- a/index.html
+++ b/index.html
@@ -47,7 +47,7 @@ <h1>Tic Tac Toe</h1>
   </tr>
 </table>
 
-<h2 hidden>Game over, refresh to play again 🧑‍💻 🤖!</h2>
+<h2 hidden>Play again for win!! 🦾🤖!</h2>
 
 <script>
   // Initialization

From fa57ba73004fec2afecd839b406c53f8da1cd920 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Sat, 2 Mar 2024 14:04:19 +0000
Subject: [PATCH 8/8] Update to 6 in STEP and README.md

---
 .github/steps/-step.txt |  2 +-
 README.md               | 15 +++++++--------
 2 files changed, 8 insertions(+), 9 deletions(-)

diff --git a/.github/steps/-step.txt b/.github/steps/-step.txt
index 7ed6ff8..1e8b314 100644
--- a/.github/steps/-step.txt
+++ b/.github/steps/-step.txt
@@ -1 +1 @@
-5
+6
diff --git a/README.md b/README.md
index c404a6d..05cce92 100644
--- a/README.md
+++ b/README.md
@@ -14,22 +14,21 @@ _Collaborate and work together on 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: Apply suggested changes
+## Step 6: Merge your pull request
 
-_Nicely done suggesting changes! :partying_face:_
+_Almost there! :heart:_
 
-Now let's see how easy it is to [apply your suggestion](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request).
+You can now [merge](https://docs.github.com/en/get-started/quickstart/github-glossary#merge) your pull request!
 
-### :keyboard: Activity: Apply suggested changes
+### :keyboard: Activity: Merge your pull request
 
-1. Click **Commit suggestion**.
-1. Type a commit message.
-1. Click **Commit changes**.
+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.
 
 <footer>