GitBook: [#190] No subject

Xiulung Choy · gitbook-bot · commit ecd49fbf6f2c · 2022-08-25T17:03:44.000Z
diff --git a/guides/graphite-cli/restacking-branches.md b/guides/graphite-cli/restacking-branches.md
@@ -2,7 +2,7 @@
 
 A key benefit of using Graphite as opposed to vanilla Git when working with stacks is dependency management for your branches, i.e. keeping track of the "parent" of a given branch.  When a parent branch changes in some way or is deleted, vanilla Git, because it does not have this concept of branch dependencies, leaves the parent as is.
 
-The Graphite CLI introduces "restacking", which is the process of ensuring that the history of a branch is updated when its parent changes.  Consider where we left off on the [previous page](https://docs.graphite.dev/guides/graphite-cli/syncing-and-resolving-conflicts) after running `gt repo sync`.  Although `part_2` is now dependent on main, we haven't yet restacked it, and we can see that by viewing the Git history with `gt log long`:
+The Graphite CLI introduces "restacking", which is the process of ensuring that the history of a branch is updated when its parent changes.  Consider where we left off on the previous page.  Although `part_2` is now dependent on main, we haven't yet restacked it, and we can see that by viewing the Git history with `gt log long`:
 
 ![log long output](<../../.gitbook/assets/image (16).png>)
 
diff --git a/guides/graphite-cli/syncing-and-resolving-conflicts.md b/guides/graphite-cli/syncing-and-resolving-conflicts.md
@@ -1,7 +1,7 @@
-# Syncing with remote
+# Syncing with remote repository
 
 {% hint style="info" %}
-Very often as you're building, the remote trunk branch will move ahead of your local repository, and you'll want to pull in the latest changes and resolve any conflicts before you land your pull requests.
+Often, as you're building, the remote trunk branch will move ahead of your local repository, and you'll want to pull in the latest changes and resolve any conflicts before you land your pull requests.
 {% endhint %}
 
 ## Syncing your repo
@@ -22,4 +22,4 @@ Now, if we run `gt log`, we see that `part_2` is based on `main`:
 
 <img src="../../.gitbook/assets/image (6).png" alt="" data-size="original">
 
-Since we didn't restack as part of the `sync` command here (we could have done so with `--restack`), we see that `part_2` needs a restack onto `main`.  We'll talk about what that means in the next section.
+Since we didn't restack as part of the `sync` command here (we could have done so with `--restack`), we see that `part_2` needs a restack onto `main`.  We'll talk about what that means in the next section: [restacking branches](https://docs.graphite.dev/guides/graphite-cli/restacking-branches).
