CHANGELOG/CHANGELOG-1.18.md: Fix spelling

[sanmai-NL]

What type of PR is this?
/kind documentation

What this PR does / why we need it:
Fix 'aggregation' spelling.

Which issue(s) this PR fixes:
Not applicable.

Special notes for your reviewer:
Not applicable.

Does this PR introduce a user-facing change?:

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: login-issues@jira.linuxfoundation.org

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[k8s-ci-robot]

Welcome @sanmai-NL!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @sanmai-NL. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sanmai-NL]

/assign @justaugustus
I've signed the CLA.

[justaugustus]

@sanmai-NL -- Please update the PR title, description, and description commit message to describe what spelling you're fixing.

Example:

CHANGELOG/CHANGELOG-1.18.md: Fix spelling

ref: https://chris.beams.io/posts/git-commit/
/hold
/ok-to-test

[sanmai-NL]

/retest

All flakes.

[justaugustus]

@sanmai-NL -- Can you address my comment before sending this for retest: #87969 (comment)

[sanmai-NL]

@justaugustus Will do. Why before?

[justaugustus]

... Why before?

@sanmai-NL -- because tests cost money 😅
Not a great answer especially since this is a markdown change, but I'm just trying to encourage good submission habits.

[sanmai-NL]

@justaugustus: Yeah, I figured that. Besides this only being a docs change, you only asked me to change some things that aren't altering the Git history, so tests wouldn't be re-run anyhow. May I propose you spend some time on limiting test runs to those that may be impacted by a change? This could save you CI budget if that's a limitation you're running into.

[sanmai-NL]

/retest

[k8s-ci-robot]

@sanmai-NL: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sanmai-NL]

@sanmai-NL: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

@justaugustus

[justaugustus]

@sanmai-NL -- Can you also update the commit message? My original message was supposed to mention that as well.

[justaugustus]

@sanmai-NL -- Did you have a chance to get back to this one?

[sanmai-NL]

Thanks for reminding. No, been too busy. Will try to fix today! If not close the PR and let your team make the typo fixes please. 🙂

[sanmai-NL]

@justaugustus: should be done now.

[justaugustus]

Thanks for the fix, @sanmai-NL (and sorry for the wait)!
/ok-to-test
/lgtm
/approve
/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: justaugustus, sanmai-NL

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• CHANGELOG/OWNERS [justaugustus]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sanmai-NL]

/retest

[sanmai-NL]

/retest