From 00f516a2ab8891cb74c0c7f9c7f28da05de401c3 Mon Sep 17 00:00:00 2001
From: Rohit Paul <113459757+RohitPaul0007@users.noreply.github.com>
Date: Tue, 2 Jan 2024 16:09:35 +0530
Subject: [PATCH] Update contributor_guidelines.md

---
 contributor_docs/contributor_guidelines.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contributor_docs/contributor_guidelines.md b/contributor_docs/contributor_guidelines.md
index a51f93103a..4f24c4ca27 100644
--- a/contributor_docs/contributor_guidelines.md
+++ b/contributor_docs/contributor_guidelines.md
@@ -208,7 +208,7 @@ Once the push is complete, you may see a link in the terminal that lets you open
 ### Pull request information
 Before filing the pull request, you will need to fill out the pull request template. First of all the pull request title should briefly describe what the changes are, again avoid generic statements here.
 
-Next, in the template, there is this line `Resolves #[Add issue number here]` which you should replace `[Add issue number here]` with the issue number of the issue you are addressing/fixing [above](#all-about-issues) (eg. `Resolves #1234`). This will make sure the issue is automatically closed after this PR is merged. If you do not wish to automatically close the issue after this PR is merged (maybe because there are more changes coming in a separate PR), change `Resovles` to `Addresses`.
+Next, in the template, there is this line `Resolves #[Add issue number here]` which you should replace `[Add issue number here]` with the issue number of the issue you are addressing/fixing [above](#all-about-issues) (eg. `Resolves #1234`). This will make sure the issue is automatically closed after this PR is merged. If you do not wish to automatically close the issue after this PR is merged (maybe because there are more changes coming in a separate PR), change `Resolves` to `Addresses`.
 
 For "Changes", you should give a clear description of the changes you have made in this PR. Include any implementation details and decisions you made here that are relevant to whoever will review this PR.