From 8df4a93875b7936051ca44976b002bbf8e9742cb Mon Sep 17 00:00:00 2001
From: itecompro <16090309+itecompro@users.noreply.github.com>
Date: Tue, 2 Apr 2024 05:05:56 +1100
Subject: [PATCH] Apply style guide to placeholders in "Syncing a fork"
 (#32313)

Co-authored-by: Alex Nguyen <150945400+nguyenalex836@users.noreply.github.com>
---
 .../working-with-forks/syncing-a-fork.md                  | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
index 33fad45f03..c3bdb3471c 100644
--- a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
+++ b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork.md
@@ -42,10 +42,10 @@ If the changes from the upstream repository cause conflicts, {% data variables.p
 
 {% data reusables.cli.about-cli %} To learn more about {% data variables.product.prodname_cli %}, see "[AUTOTITLE](/github-cli/github-cli/about-github-cli)."
 
-To update the remote fork from its parent, use the `gh repo sync -b BRANCHNAME` subcommand and supply your fork and branch name as arguments.
+To update the remote fork from its parent, use the `gh repo sync -b BRANCH-NAME` subcommand and supply your fork and branch name as arguments.
 
 ```shell
-gh repo sync owner/cli-fork -b BRANCH_NAME
+gh repo sync owner/cli-fork -b BRANCH-NAME
 ```
 
 If the changes from the upstream repository cause conflict then the {% data variables.product.prodname_cli %} can't sync. You can set the `--force` flag to overwrite the destination branch.
@@ -56,7 +56,7 @@ Before you can sync your fork with an upstream repository, you must configure a
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 1. Change the current working directory to your local project.
-1. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCHNAME` will be stored in the local branch `upstream/BRANCHNAME`.
+1. Fetch the branches and their respective commits from the upstream repository. Commits to `BRANCH-NAME` will be stored in the local branch `upstream/BRANCH-NAME`.
 
    ```shell
    $ git fetch upstream
@@ -64,7 +64,7 @@ Before you can sync your fork with an upstream repository, you must configure a
    > remote: Compressing objects: 100% (53/53), done.
    > remote: Total 62 (delta 27), reused 44 (delta 9)
    > Unpacking objects: 100% (62/62), done.
-   > From https://{% data variables.command_line.codeblock %}/ORIGINAL_OWNER/ORIGINAL_REPOSITORY
+   > From https://{% data variables.command_line.codeblock %}/ORIGINAL-OWNER/ORIGINAL-REPOSITORY
    >  * [new branch]      main     -> upstream/main
    ```