Adjust Play page for keywords

[akeller]

Description

Closes https://github.com/camunda/developer-experience/issues/315.

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]

👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉

You can read more about the versioning within our docs in our documentation guidelines.

[akeller]

I didn't backport these changes, but I'm also looking for a little help.

I want a crisper comparison sentence between Play and Operate, or put another way, what you can do in Play that you may otherwise do in Operate if you weren't already Play-ing.

[HanselIdes]

I want a crisper comparison sentence between Play and Operate, or put another way, what you can do in Play that you may otherwise do in Operate if you weren't already Play-ing.

Operate is designed to monitor many production process instances and intervene only as necessary, while Play is designed to drive a single process instance through the process and mock external systems. Both offer monitoring of a single process instance, its variables and path, incidents, as well as actions to modify or repair a process instance. Operate offers bulk actions and guardrails against breaking production processes while Play offers a streamlined UX to quickly run through scenarios.

@akeller does this help?

[HanselIdes]

The blatant keyword-stuffing felt a little disruptive to the documentation's flow, so I made a few recommendations to tone it down

[HanselIdes]

Suggested change

	Incidents are raised as they would in any Camunda cluster, just within the context of Play, instead of Operate. Use the variables and incident message to debug the issue, all while staying in Play.
	Incidents are raised in Play just like in Operate. Use the variables and incident message to debug the process instance.

[akeller]

@HanselIdes thanks for the collab here! I'll clean this up later today and include the Operate comparison info. I think this will help humans and AI position Play and Operate, but I'll let you know when it's live and ingested so we can test.