From 6f6ec0925eca4f60400e60aa067eb6a77b7105e1 Mon Sep 17 00:00:00 2001 From: Triya Verma <125420118+PythiaUF@users.noreply.github.com> Date: Tue, 10 Sep 2024 18:42:13 -0400 Subject: [PATCH] fix: typo --- docs/club/resources/pr_review.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/club/resources/pr_review.md b/docs/club/resources/pr_review.md index bc05cc2..7193608 100644 --- a/docs/club/resources/pr_review.md +++ b/docs/club/resources/pr_review.md @@ -7,7 +7,7 @@ sidebar_position: 8 # Reviewing Pull Requests :::note -This guide assumes you already have your own clone of the respotiory based on your own fork (or the main project). +This guide assumes you already have your own clone of the repository based on your own fork (or the main project). ::: If you are someone in charge of reviewing pull requests for an open source repository on GitHub (like a tech lead), you'll need to know how to review pull requests. This guide will help you understand the process of reviewing pull requests and how to provide feedback to contributors. @@ -132,4 +132,4 @@ In the above image, the dropdown button next to the main button has been clicked - "Squash and merge": This will squash all the commits from the pull request into a single commit and merge it into the main branch. This is useful if the pull request has multiple commits that you want to combine into a single commit. - "Rebase and merge": This will rebase the changes from the pull request onto the main branch and merge them. This only works if there's no conflicts. However, this means that there is no merge commit, which can make the history cleaner. -Choose the appropriate option and click the "Confirm merge" button to merge the pull request. \ No newline at end of file +Choose the appropriate option and click the "Confirm merge" button to merge the pull request.