From 8d8a0b328fd8bab7cc7d1691c9c480712eaa2c2e Mon Sep 17 00:00:00 2001
From: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Date: Wed, 22 Jul 2020 14:04:58 +0200
Subject: [PATCH] Rewrite overly long sentence

---
 book/03-git-branching/sections/rebasing.asc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/book/03-git-branching/sections/rebasing.asc b/book/03-git-branching/sections/rebasing.asc
index 726f5fc78..6e47214b1 100644
--- a/book/03-git-branching/sections/rebasing.asc
+++ b/book/03-git-branching/sections/rebasing.asc
@@ -235,4 +235,4 @@ Now, to the question of whether merging or rebasing is better: hopefully you'll
 Git is a powerful tool, and allows you to do many things to and with your history, but every team and every project is different.
 Now that you know how both of these things work, it's up to you to decide which one is best for your particular situation.
 
-In general the way to get the best of both worlds is to rebase local changes you've made but haven't shared yet before you push them in order to clean up your story, but never rebase anything you've pushed somewhere.
+You can get the best of both worlds: rebase local changes before pushing to clean up your work, but never rebase anything that you've pushed somewhere.
\ No newline at end of file