From 1fc1ac186cf28d23dee72bd9ae324dfbac9f2bd5 Mon Sep 17 00:00:00 2001
From: Neeraj Kumar <susenj@users.noreply.github.com>
Date: Wed, 25 May 2022 20:17:04 +0530
Subject: [PATCH] git rebase usecase updated (#246)

* Edited couple answers in the Network section

* Edited Latency, Throughput and bandwidth

* Edited few more answers in the Linux section

* typos

* git rebase usecase update
---
 exercises/git/README.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/exercises/git/README.md b/exercises/git/README.md
index 1abd82f..b8de1ae 100644
--- a/exercises/git/README.md
+++ b/exercises/git/README.md
@@ -177,6 +177,7 @@ Using the `git rebase` command
 
 <details>
 <summary>In what situations are you using <code>git rebase</code>?</summary><br><b>
+Suppose a team is working on a `feature` branch that is coming from the `main` branch of the repo. At a point, where the feature development is done, and finally we wish to merge the feature branch into the main branch without keeping the history of the commits made in the feature branch, a `git rebase` will be helpful. 
 </b></details>
 
 <details>