Update generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md

[cdiamon]

Why:

The wording can be misleading: 'later' version can be read as 'older' as well as 'newer'

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

update wording for more clarity since 'later' can be read as 'older' or 'newer'

Check off the following:

• [ ] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

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

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

[welcome[bot]]

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

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
authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md	fpt ghec ghes@ 3.9 3.8 3.7 3.6 3.5 3.4 ghae	fpt ghec ghes@ 3.9 3.8 3.7 3.6 3.5 3.4 ghae

---

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

[cmwilson21]

@cdiamon Thanks so much for opening a PR! I'll get this triaged for review :zap:

[am-stead]

Hi @cdiamon,

Thanks so much for opening a PR!

We do generally use "or later" throughout our docs to denote newer software versions, since this aligns with the our style guide conventions (we defer to the Microsoft Style Guide).

I will close this PR for now. Thank you for taking the time to contribute! ✨