Clarify "removing secrets from previous commits" section

[lacymorrow]

Why:

I've run into this issue multiple times.

In the sections to "Removing a secret introduced by...", following the steps as described will not do anything. Git is used by folks who are not get experts, therefore we should describe each step fully.

Check off the following:

• I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

  • For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

• For content changes, I have completed the self-review checklist.

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

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
code-security/secret-scanning/working-with-secret-scanning-and-push-protection/working-with-push-protection-from-the-command-line.md	fpt ghec ghes@ 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.14 3.13 3.12 3.11 3.10

---

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

[mchammer01]

@lacymorrow - thanks so much for spotting these inaccuracies and omissions ✨
Made a minor change to do with wording that I am going to apply.

[mchammer01]

LGTM

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

[lacymorrow]

Thanks folks! I ran into the issue again today 😅

[mchammer01]

What do you mean @lacymorrow? Your updates are in the docs. Do these need further tweaking?

[nguyenalex836]

I think @lacymorrow was expressing gratitude for the update to the docs, as she ran into a scenario again where clarity on these steps helped her 💛 But let me know if I am off!