feat: add explanation about commit message in the README

README.md

@@ -99,29 +99,30 @@ First, you'll want to have Node.js installed. You can do this by going to [nodej
 
 7. If you used the CLI tool method in step 5 to add yourself to the guest book, **skip this step**. Otherwise:
 
-   Add and commit your changes by running this command:
+   Add and commit your changes by running the following  command:
 
    ```bash
    git commit -am "Your message"
    ```
 
    Change `"Your message"` to your own message. For example, `"Add Alice as a contributor"`.
+Unlike the `git add .` and  `git commit -m "Your message"` approach, the `git commit -am` command skips the staging process. This is because its use of `-a` automatically stage the changes you made via Git.
 
-8. Run `git log` to check if you have committed your changes. Press `Q` to close the log.
+1. Run `git log` to check if you have committed your changes. Press `Q` to close the log.
 
    If you add yourself using the CLI tool, it automatically adds and commits your changes. So you will see this automated commit message:
 
    ```bash
    docs: add @your_username as a contributor
    ```
 
-9. Push the commit to your forked repository with this command:
+2. Push the commit to your forked repository with this command:
 
    ```bash
    git push -u origin branch-name
    ```
 
-10. Go to your forked repository on GitHub and [create a 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-from-a-fork) with the title `feat: Add <@github-username> as a contributor`.
+3.  Go to your forked repository on GitHub and [create a 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-from-a-fork) with the title `feat: Add <@github-username> as a contributor`.
 
 ## Keeping Branch Up to Date and Resolving Merge Conflicts