Fix typo in #4412

[akeller]

Description

Follow up to typo in #4412.

@camunda/tech-writers please do a retro review on #4412. You can adjust this PR if you'd like to capture any additional changes.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

[github-actions]

👋 🤖 🤔 Hello! Did you make your changes in all the right places?

These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.

• docs/self-managed/operational-guides/update-guide/860-to-870.md

You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines.

[mesellings]

Lgtm - just one comment to check 👍

[mesellings]

Is this correct? (8.7.0) As we say 8.7.x for the components? I assume so, but just checking 👍

[akeller]

This is what we've historically done for Self-Managed. It follows the linked release notes tag and other release artifacts. Bring the topic to the Tech Writer sync if you want to discuss changing it.