Fixed typo for new git url.

[patcon]

Sorry, there was too much issue boilerplate for such a small fix, so I didn't read any of it. Thanks for understanding -- pls close if you can't merge 🙏

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

👓 Previews for changed content

This comment is 🤖 automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the review server. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10

---

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server
This table is posted from the Content Changes Table Comment workflow.

[Lowprofile666-hub]

Thank You 😘👍

[dejadior440]

+

[dejadior440]

content/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository.md

[Lowprofile666-hub]

Thank you I will figure out

[subatoi]

Hi, I'm not sure this change is necessarily appropriate, but thank you for your interest in the docs

Please feel free to take a look at our issues marked help wanted, but I'm going to go ahead and close this one out. Thanks again!

[patcon]

In case the context was lost in the noise, this is the current state of the doc. It is confusing because it's misleading right now. If I didn't know git, I might be thrown off by why the "verify the remote" step shows a different url than the preceding "set the remote" step.

https://docs.github.com/en/get-started/using-git/splitting-a-subfolder-out-into-a-new-repository

I don't particularly have much stake in this game, nor do I know the contribution flow, but I would humbly suggest some improvement be made to this one line.

Anyhow, thanks for all you do!

[patcon]

REPOSITORY-NAME is used for the original repo further above, so it's unclear what's being suggested, if a person is new to git.

So if someone is following this contradictory advice, they might easily add the original remote, thinking that's the intention. And if they know enough about force-push to try it when they get a conflict warning, they might override their original repo, mistakenly assured earlier in the doc that the instructions on the page are guiding them through a non-destructive process.

Sorry if I'm way off-base and misunderstanding