Change to git add renormalize command after changing line endings

[mems]

Why:

I follow the instructions of "Refreshing a repository after changing line endings", but after normalize all files in a repo, some files still unnormalized (when I switch branches or merge, these "fantom-changes-that-can't-be-undo" appears).
After few search on the web, I found the mentioned command (git rm -rf --cached . ; git reset --hard HEAD) aren't recommended in git doc, but git add --renormalize . is since git 2.16 ("a new and safer way to record the fact that you are correcting the end-of-line convention").
Before it was use different command combinations:

• git/git@9472935#diff-8c2ad6307733b92b3f5a6a70a3f3bbe1076c0fdf4da66c3633f90d15c6cf118aL235
• git/git@773a889#diff-8c2ad6307733b92b3f5a6a70a3f3bbe1076c0fdf4da66c3633f90d15c6cf118aL232
• git/git@8599974#diff-8c2ad6307733b92b3f5a6a70a3f3bbe1076c0fdf4da66c3633f90d15c6cf118aL230
• git/git@fd6cce9#diff-8c2ad6307733b92b3f5a6a70a3f3bbe1076c0fdf4da66c3633f90d15c6cf118aR209

What's being changed (if available, include any code snippets, screenshots, or gifs):

Change the snippet to use the command that normalize all files

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require a SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing.

[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.

[nguyenalex836]

@mems Thanks so much for opening a PR! I'll get this triaged for review ✨

[github-actions]

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

[nguyenalex836]

@mems Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏

[github-actions]

Automatically generated comment ℹ️

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 staging site. 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/getting-started-with-git/configuring-git-to-handle-line-endings.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

---

fpt: Free, Pro, Team
ghec: GitHub Enterprise Cloud
ghes: GitHub Enterprise Server

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡