scaleracademy · shubhansu-kr · Sep 5, 2022 · Sep 5, 2022 · Sep 7, 2022 · Sep 12, 2022
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,9 +1,10 @@
-## Contributing Guidelines
+# Contributing Guidelines
 
 Thank you for considering contributing to the repository. This guide details all the general information that one should know before contributing to the project.
 Please stick as close as possible to the guidelines. That way we ensure that you have a smooth experience contributing to this project.
 
-### General Rules :
+## General Rules
+
 These are in general rules that you should be following while contributing to an Open Source project :
 
 - Be Nice, Be Respectful (BNBR)

diff --git a/Challenges/challenge_1.md b/Challenges/challenge_1.md
@@ -1,12 +1,12 @@
-## Welcome to Challenge 1
+# Welcome to Challenge 1
 
-Welcome to the first challenge! 
-We will start off with an easy task. 
+Welcome to the first challenge!
+We will start off with an easy task.
 
-Task: 
-Create a [new issue](https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/new) on this repository with the following details to be added to the content of the issue: 
+Task:
+Create a [new issue](https://github.com/scaleracademy/scaler-september-open-source-challenge/issues/new) on this repository with the following details to be added to the content of the issue:
 
-```
+```text
 name: Add your name here
 github_user_name: add your github username here
 ```
diff --git a/Challenges/challenge_10.md b/Challenges/challenge_10.md
@@ -1,22 +1,24 @@
-## Welcome to Challenge 10
+# Welcome to Challenge 10
 
-Welcome to the 10th challenge! 
+Welcome to the 10th challenge!
 
-Today's challenge is based on the concept of signing your commits. Signing the commits is a way of showing that only authentic commits are being made. 
+Today's challenge is based on the concept of signing your commits. Signing the commits is a way of showing that only authentic commits are being made.
 
-A lot of open source projects have DCO which stands for [Developer Certification of Origin](https://github.com/apps/dco) including this repository itself and it tries to verify that each commit is signed or not. In case your commit is not signed it will reflect in the pull request that it doesn't pass the DCO test. 
+A lot of open source projects have DCO which stands for [Developer Certification of Origin](https://github.com/apps/dco) including this repository itself and it tries to verify that each commit is signed or not. In case your commit is not signed it will reflect in the pull request that it doesn't pass the DCO test.
 
 You can read more about how to sign commits [here](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits)
 
-Task: 
-1. Setup the ability to sign commits locally in your systems 
-2. Whenever committing in the future always try to use signed commits 
-3. Make a new signed commit to the pull request that you have made in previous challenges by making this change to the ``yourusername.md`` file: 
-```
----
-name: your_name
-github_user_name: YOUR-GITHUB-USERNAME
-url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge
-your_favroite_programming_language: Add your favorite programming language here
----
-```
+Task:
+
+1. Setup the ability to sign commits locally in your systems
+2. Whenever committing in the future always try to use signed commits
+3. Make a new signed commit to the pull request that you have made in previous challenges by making this change to the ``yourusername.md`` file:
+
+    ```text
+    ---
+    name: your_name
+    github_user_name: YOUR-GITHUB-USERNAME
+    url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge
+    your_favroite_programming_language: Add your favorite programming language here
+    ---
+    ```
diff --git a/Challenges/challenge_11.md b/Challenges/challenge_11.md
@@ -1,9 +1,10 @@
-## Welcome to Challenge 11
+# Welcome to Challenge 11
 
-Welcome to the 11th challenge! 
+Welcome to the 11th challenge!
 
 Today's challenge is simple.
 
-Task: 
-1. Create another branch from your current branch created in previous challenges (Don't create a new branch from main). 
+Task:
+
+1. Create another branch from your current branch created in previous challenges (Don't create a new branch from main).
 2. Share screenshot of this new branch in the issue created in previous challenge
diff --git a/Challenges/challenge_12.md b/Challenges/challenge_12.md
@@ -1,14 +1,15 @@
-## Welcome to Challenge 12
+# Welcome to Challenge 12
 
-Welcome to the 12th Challenge 
+Welcome to the 12th Challenge
 
-Today's challenge is a re-practice of the 7th Challenge (https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_7.md?plain=1)
+Today's challenge is a re-practice of the 7th Challenge (<https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_7.md?plain=1>)
 
-So focus for this challenge will be to practice the ``git rebase`` command. We still see a number of Pull requests that have a lot more commits than there should be, therefore we give you a chance to correct it again. 
+So focus for this challenge will be to practice the ``git rebase`` command. We still see a number of Pull requests that have a lot more commits than there should be, therefore we give you a chance to correct it again.
 
-Ensure to practice the ``git rebase`` command by creating your own local git repository. You can checkout this guide: https://www.freecodecamp.org/news/git-squash-explained/
+Ensure to practice the ``git rebase`` command by creating your own local git repository. You can checkout this guide: <https://www.freecodecamp.org/news/git-squash-explained/>
 
-Task: 
-1. Practice git rebase, and how to squash commit using git rebase in your local projects 
+Task:
+
+1. Practice git rebase, and how to squash commit using git rebase in your local projects
 2. Once done, try to squash the commits in your pull request in the Challenge repository
-3. We also see a lot of challengers are not signing their commits. Refer to Challenge 10: https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_10.md and ensure to sign your commits. 
+3. We also see a lot of challengers are not signing their commits. Refer to Challenge 10: <https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_10.md> and ensure to sign your commits.
diff --git a/Challenges/challenge_13.md b/Challenges/challenge_13.md
@@ -1,10 +1,11 @@
-## Welcome to Challenge 13
+# Welcome to Challenge 13
 
-Welcome to the 13th Challenge 
+Welcome to the 13th Challenge
 
 Today's challenge involves how to use ``git stash`` command effectively. You can refer on how to stash your commits [here](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning)
 
-Task: 
+Task:
+
 1. Inside the branch you created in the previous challenge ``your-username-details`` create a new file inside the ``contributors/<YOUR-GITHUB_USERNAME>/`` directory.
 2. Use the git stash command to move these changes to the stash area
-3. Delete the content from the stash area and share a screenshot of this inside the Github issue you created in the first challenge
+3. Delete the content from the stash area and share a screenshot of this inside the GitHub issue you created in the first challenge
diff --git a/Challenges/challenge_14.md b/Challenges/challenge_14.md
@@ -1,11 +1,12 @@
-## Welcome to Challenge 14
+# Welcome to Challenge 14
 
-Welcome to the 14th Challenge 
+Welcome to the 14th Challenge
 
-Today is the first part of the two challenges related to resolving merge conflicts. You can take a look at [this article](https://www.atlassian.com/git/tutorials/using-branches/merge-conflicts) to learn more about merge conflicts. 
+Today is the first part of the two challenges related to resolving merge conflicts. You can take a look at [this article](https://www.atlassian.com/git/tutorials/using-branches/merge-conflicts) to learn more about merge conflicts.
 
-As part of the challenge, try to create a scenario of a merge conflict locally in your system for a project that you can create. 
+As part of the challenge, try to create a scenario of a merge conflict locally in your system for a project that you can create.
 
-Task: 
-1. Follow the article shared above and try to reproduce a case of merge conflict in your system for a project and try to resolve it 
-2. Share appropriate screenshot in the issue created in the first challenge. 
+Task:
+
+1. Follow the article shared above and try to reproduce a case of merge conflict in your system for a project and try to resolve i
+2. Share appropriate screenshot in the issue created in the first challenge.
diff --git a/Challenges/challenge_15.md b/Challenges/challenge_15.md
@@ -1,15 +1,15 @@
-## Welcome to Challenge 15
+# Welcome to Challenge 15
 
-Welcome to the 15th Challenge 
+Welcome to the 15th Challenge
 
-In this 2 part challenge, we will try to emulate and fix merge conflicts via git. 
+In this 2 part challenge, we will try to emulate and fix merge conflicts via git.
 
-Today is the first part of this challenge: 
+Today is the first part of this challenge:
 
-Task: 
-1. Update your Forked Repo From the Original Repo. Also ensure that your branch ``your-user-name-details`` is also synced with the latest changes from the original repository
+Task:
 
-2. In your branch ``your-user-name-details`` open the add your name to the list of challengers inside the ``challengers-list.md`` file by following the format in the file. 
+1. Update your Forked repository From the Original repository. Also ensure that your branch ``your-user-name-details`` is also synced with the latest changes from the original repository
 
-3. Push your change to reflect in the Pull Request created in previous challenges
+2. In your branch ``your-user-name-details`` open the add your name to the list of challengers inside the ``challengers-list.md`` file by following the format in the file.
 
+3. Push your change to reflect in the Pull Request created in previous challenges
diff --git a/Challenges/challenge_16.md b/Challenges/challenge_16.md
@@ -1,14 +1,13 @@
-## Welcome to Challenge 16
+# Welcome to Challenge 16
 
-Welcome to the 16th Challenge 
+Welcome to the 16th Challenge
 
-In this 2 part challenge, we will try to emulate and fix merge conflicts via git. 
+In this 2 part challenge, we will try to emulate and fix merge conflicts via git.
 
-Today is the second and final part of this challenge: 
+Today is the second and final part of this challenge:
 
-Task: 
-1. You will notice that your pull request will have a conflict: <img width="636" alt="image" src="https://user-images.githubusercontent.com/19529592/190574995-0cc506a8-a2fe-4aa4-98bd-4658e8aa2fc1.png">
+Task:
 
-2. Try to resolve this merge conflict using local git 
-
-3. Once resolved, share screenshot on the github issue created in the previous challenges
+1. You will notice that your pull request will have a conflict:
+2. Try to resolve this merge conflict using local git
+3. Once resolved, share screenshot on the GitHub issue created in the previous challenges
diff --git a/Challenges/challenge_2.md b/Challenges/challenge_2.md
@@ -1,11 +1,14 @@
-## Welcome to Challenge 2
+# Welcome to Challenge 2
 
-Welcome to the second challenge! 
+Welcome to the second challenge!
 Today we will focus on how to fork and create a clone of a Github repository
 
-Task: 
-1. Create a fork of this repository 
-2. Clone the forked project locally in your system using the ``git clone`` command 
-3. Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following: 
-- URL of your forked repository 
+Task:
+
+1. Create a fork of this repository
+2. Clone the forked project locally in your system using the ``git clone`` command
+
+3. Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following:
+
+- URL of your forked repository
 - A screenshot of the cloned project in your system
diff --git a/Challenges/challenge_3.md b/Challenges/challenge_3.md
@@ -1,10 +1,13 @@
-## Welcome to Challenge 3
+# Welcome to Challenge 3
 
-Welcome to the third challenge! 
+Welcome to the third challenge!
 Today we will focus on how to create a new branch in a git repository
 
-Task: 
+Task:
+
 1. Following up on the [previous task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_2.md), create a new branch locally in your forked clone repository
 2. The branch name should be as follows: ``your_github_username-details``. Example: ``shivaylamba-details``
+
 3. Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following:
+
 - Screenshot showing the list of all the current branches inside of your forked clone repository
diff --git a/Challenges/challenge_4.md b/Challenges/challenge_4.md
@@ -1,11 +1,14 @@
-## Welcome to Challenge 4
+# Welcome to Challenge 4
 
-Welcome to the fourth challenge! 
+Welcome to the fourth challenge!
 Today we cover how to Update Fork Repo From the Original Repo
 
 The main repository has been updated since the last fork that all of you created. The goal is to updated the forked repository with the changes made in the original repository. This can be done with the git command of ``git remote add upstream``
 
 Task
+
 1. Update your forked repository locally with the content of the original repository for both the main branch and the branch that you created in Challenge 3 using the ``git remote add upstream`` command
+
 2. Once the changes in the forked repository and the original repository are synced in the git branch that you created in the 3rd Challenge, Add a new comment to the issue you created in the [first task](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_1.md). The comment should have the following:
-- Screenshot showing the latest repository contents
+
+- Screenshot showing the latest repository contents
diff --git a/Challenges/challenge_5.md b/Challenges/challenge_5.md
@@ -1,28 +1,37 @@
-## Welcome to Challenge 5
+# Welcome to Challenge 5
+
+Welcome to the fifth challenge
+
+Welcome to the fourth challenge!
 
-Welcome to the fifth challenge! 
 Today's goal is to update your forked repository and then create a Pull Request
 
 Task
+
 1. Ensure your forked repository is in sync with the latest changes in the main repository. Also ensure that the git branch that you created in Challenge 2 is also in sync with the latest changes
 2. Create a new folder inside the `contributors` folder, and name it with your github username. It should look something like this `contributors/<YOUR-GITHUB_USERNAME>/`. Ex.
 
-```
-contributors/shivaylamba/
-```
+    ```text
+    contributors/shivaylamba/
+    ```
 
 3. Create a markdown file in the folder you created following the naming convention for the file: `<YOUR-GITHUB-USERNAME>.md`. Ex.
 
-```
-contributors/shivaylamba/shivaylamba.md
-```
+    ```text
+    contributors/shivaylamba/shivaylamba.md
+    ```
 
 4. Copy the following template into your file, delete the placeholder text and fill the information with yours.
 
-```
----
-name: your_name
-github_user_name: YOUR-GITHUB-USERNAME
----
-```
+    ```text
+    ---
+    name: your_name
+    github_user_name: YOUR-GITHUB-USERNAME
+    ---
+    ```
+
 5. Submit your Pull Request on the main challenge repo.
+
+6. Submit your Pull Request
+
+>>>>>>> e5a28d5 (Challenge 5)
diff --git a/Challenges/challenge_6.md b/Challenges/challenge_6.md
@@ -1,19 +1,23 @@
-## Welcome to Challenge 6
+# Welcome to Challenge 6
 
-Welcome to the sixth challenge! 
+Welcome to the sixth challenge!
 Today's goal is to update your pull request that you created in [Challenge 5](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_5.md?plain=1)
 
 Task
-1. Create a new commit in the branch you created in Challenge 2 in your forked repository 
-2. The change that you have to make should be the following: 
-In the markdown file that was created in Challenge 5, edit the details as follows: 
-```
----
-name: your_name
-github_user_name: YOUR-GITHUB-USERNAME
-url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge
----
-```
-3. After making this change create a commit with a proper commit message and push the changes 
-4. Check if the commit reflects in the Pull request you created in Challenge 5
 
+1. Create a new commit in the branch you created in Challenge 2 in your forked repository
+
+2. The change that you have to make should be the following:
+In the markdown file that was created in Challenge 5, edit the details as follows:
+
+    ```text
+    ---
+    name: your_name
+    github_user_name: YOUR-GITHUB-USERNAME
+    url_of_github_issue: Link_of_the_github_issue_created_in_first_challenge
+    ---
+    ```
+
+3. After making this change create a commit with a proper commit message and push the changes
+
+4. Check if the commit reflects in the Pull request you created in Challenge 5
diff --git a/Challenges/challenge_7.md b/Challenges/challenge_7.md
@@ -1,9 +1,10 @@
-## Welcome to Challenge 7
+# Welcome to Challenge 7
 
-Welcome to the seventh challenge! 
+Welcome to the seventh challenge!
 Today's goal is to implement the squashing of the git commits. Squashing is used to combine multiple commits into one. This is done using the interactive mode of Git Rebase command.
-In the [6th Challenge](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_6.md?plain=1) all of you created an additional commit to update the markdown file. 
-So refer to [this guide](https://www.freecodecamp.org/news/git-squash-explained/) on Git merge. 
+In the [6th Challenge](https://github.com/scaleracademy/scaler-september-open-source-challenge/blob/main/Challenges/challenge_6.md?plain=1) all of you created an additional commit to update the markdown file.
+So refer to [this guide](https://www.freecodecamp.org/news/git-squash-explained/) on Git merge.
 
-Task: 
-1. Using the interactive mode of Git Rebase command combine the multiple commits created in your Pull requests and then push that to the Pull request you have created in the previous challenges. 
+Task:
+
+1. Using the interactive mode of Git Rebase command combine the multiple commits created in your Pull requests and then push that to the Pull request you have created in the previous challenges.
diff --git a/Challenges/challenge_8.md b/Challenges/challenge_8.md
@@ -1,11 +1,11 @@
-## Welcome to Challenge 8
+# Welcome to Challenge 8
 
-Welcome to the 8th challenge! 
+Welcome to the 8th challenge!
 
 Today's challenge is simple. But along side the task, please give the [following article](https://www.atlassian.com/git/tutorials/undoing-changes/git-reset) a read, as this will be used in Challenge 9.
 
+Task:
 
-Task: 
 1. Inside the branch you created during the prior challenges in your forked repository, make a new file by the name of ``your-github-username-2.md`` and add any details you may want to add to this markwdown file and push the change
 
 2. Ensure the change appears in the Pull request created in previous challenges