Hi Vipul, This is a great question. DVC does have a lot of common commands as Git. However, not all of them serve the same purpose; the `add` command is one of them. The Git add command adds the changes in the working directory to the staging area. It tells Git that you want to include updates to a particular file in the next commit. However, the dvc add command tracks the files and stages them by creating a corresponding .dvc file. It acts as a combination of the Git add and the Git commit commands. In our case, we already tracked the Universe.txt file with DVC. Hence, we could choose rather use dvc add or dvc commit to track the changes. The results of running both of these commands will be the same. You raised an excellent point referring to DVC pipelines. In a use-case where DVC tracks a file in a pipeline (meaning the md5 hash is held in a dvc.lock and not in a .dvc file), and we want to track the changes outside the pipeline - we can only use the dvc commit command. By running this command, DVC will update the md5 hash in the dvc.lock. If running the dvc add command, it will fail with a message of "overlap tracking". This is because DVC is trying to create an md5 hash in a .dvc pointer file in addition to the md5 hash of the file in the dvc.lock file. I hope it helped you understand the workflow better. If you have any further questions, feel free to ask them here or on our Discord channel -discord.com/channels/698874030052212737/737944278692790343