DOC: Fix release note typo

[dsaxton]

No description provided.

[simonjayhawkins]

Thanks @dsaxton merge when green-ish

[lumberbot-app]

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

$ git checkout 1.1.x
$ git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

$ git cherry-pick -m1 fe09a17e865995ddfe4e617031e382cd1321586a

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

$ git commit -am 'Backport PR #36670: DOC: Fix release note typo'

4. Push to a named branch :

git push YOURFORK 1.1.x:auto-backport-of-pr-36670-on-1.1.x

5. Create a PR against branch 1.1.x, I would have named this PR:

"Backport PR #36670 on branch 1.1.x"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free to suggest an improvement.

[simonjayhawkins]

probably need to wait till #36669 merged to do backport.

[dsaxton]

probably need to wait till #36669 merged to do backport.

Ok, should I go ahead and open the backport PR? I have it ready.

[simonjayhawkins]

yep. likely have conflicts if created b4 merge.

[simonjayhawkins]

it's typically that normally need to trigger the backport and when you don't want it, it works.