Update squash_and_merge_summary.md

[mdmower-csnw]

Revise terminology from "original" change to "consolidated" changes to better describe what gets committed when squashing commits.

Why:

The final sentence of the squash and merge summary confusingly describes squashing commits as retaining "original" changes. That isn't accurate. Consolidated changes are kept from squashing commits.

Closes: #36456

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

Only the final sentence of the reusable squash-and-merge-summary snippet is updated.

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 an 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 and the changes look good in the review environment.

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

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment
• Message #docs-engineering on Slack for a staging server.

A Hubber will need to deploy your changes internally to review.

Table of review links

⚠️ Warning: Our review server is experiencing latency issues.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on the review server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/about-pull-request-merges.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11	from reusable
repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/about-merge-methods-on-github.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11	from reusable

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

🤖 This comment is automatically generated.

[subatoi]

Hi @mdmower-csnw and many thanks for raising a PR and linking it to an issue — I agree that the original text is confusing, but I've suggested a different improvement which is less tied to the original text. Many thanks for your interest in the GitHub docs!

[subatoi]

Thanks again @mdmower-csnw! We really appreciate you taking the time to open an issue as well. I'll get this merged now.

Thanks again for your interest in the Docs!

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