docs: changing the reset to clear

[ana-vinogradova-camunda]

Description

As there might be multiple task listeners that are triggered in sequence, the word reset might be misleading as it may imply that a previously made correction can be "reset" (i.e. undone).

Solution: using clear instead of reset

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, @ana-vinogradova-camunda! 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/apis-tools/zeebe-api/gateway-service.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.

[akeller]

@ana-vinogradova-camunda is this part of the 8.7 minor or alpha3? When can this be merged and released?

[ana-vinogradova-camunda]

@ana-vinogradova-camunda is this part of the 8.7 minor or alpha3? When can this be merged and released?

This is a part of alpha3, just a re-wording PR (for more clarity). Can be merged asap.