Updated README.md

README.md

@@ -1,5 +1,5 @@
 <img align="center" height="500" src="https://github.com/Ishaan28malik/Hacktoberfest-2021/blob/master/src/Selection_116.png"/>
-* When the **Hacktoberfest20** comes to an end, I will be distributing some free Open Source **t-shirts** to a few contributors
+When the **Hacktoberfest20** comes to an end, I will be distributing some free Open Source **t-shirts** to a few contributors
 <h1 align=center> Hacktoberfest2021 </h1>
 
  Hacktoberfest encourages participation in the open source community, which grows bigger every year. Complete the 2021 challenge and earn a limited edition T-shirt.
@@ -20,36 +20,85 @@
 ### 1. Fork the Project
 Fork this repository and make changes in code as required. You can change it online or by cloning it in your device. Then Pust it on your Forked Repo for further Actions. Do not use special characters in the template above.
 
-### 2. Write a Good Commit Message
-You have written some code in your branch, and are ready to commit. So, make sure to written good, clean commit messages. Let's review the anatomy of a commit message.
+### 2. Write a Good Commit Message:
 
+**Once you’ve written code in your branch and are ready to commit, make sure to write clean, meaningful commit messages. Let’s review the anatomy of a good commit message:**
 
----
-First line, no more than 50 characters
+- First line: no more than 50 characters.
 
-Details section, as long as you want. Not always necessary, but
-available if you need it. Wrapped at 72 characters. Present imperative
-tense is preferred for commits. That means "fix bug", not "fixes bug" or
-"fixed bug".
 
-- Use bullets if you need
-- Bullets are a good way to summarize a few things
+- Details section (if necessary): wrapped at 72 characters, using present imperative tense like "fix bug" rather than "fixed bug."
 
-If you have too much info here, it might be a good candidate to break
-down into multiple commits. You can use emoji here too :sparkles:
 
----
+
+### Pro Tip: Use bullets or emojis if it helps to summarize:**
+
+
+◉ Bullets help summarize key points.
+
+
+◉ Too much info? Break it down into multiple commits.
+
+
+✨Emojis like ✨ can make it fun!
 
 
 ### 3. Lastly, submit your Pull Request
 Go through the checklist on the pull request template to guarantee your submission is valid. Our team will review your application, approve and merge your submission if everything is correct. Otherwise, you will get notified of the changes requested in the pull request comment section.
 
 *Note:* Don't Forget to add `hacktoberfest-accepted` Label.
 
+## Prerequisites:
+
+**Before you begin, ensure you have the following installed:**
+
+◉ Git: Version control system to manage your changes.
+--> https://git-scm.com/
+
+◉ GitHub Account: Sign up at https://github.com/
+
+◉ Code Editor: Any code editor of your choice (e.g., VSCode, Sublime Text, etc.).
+
+◉ Basic knowledge of Git and GitHub to manage repositories and pull requests.
+
+## Usages:
+
+1. **Clone the Repository**
+
+    ```
+    git clone https://github.com/your-username/repository-name.git
+
+2. **Get in the Project Directory**
+
+    ```
+    cd repository-name
+
+3. Make Your Changes Edit files or add new files as per the contribution guidelines.
+
+4. Commit Your Changes
+
+    ```
+    git add .
+
+    git commit -m "Your commit message here"
+
+5. Push to Your Fork
+
+   ```
+   git push origin branch-name
+
+6. Create a Pull Request:
+
+   ◉ Head over to your forked repository on GitHub.
+
+   ◉ Click on “Compare & Pull Request” and submit your changes.
+
+   ◉ Wait for the review and merge process!
+
 
 Please check first and then send your codes with description.
 
-*All the best for the event *
+*All the best for the event*
 
 
 ### Show some ❤ by starring the repository.