Align docs with open source edition wording#119
Merged
Conversation
kthoms
approved these changes
Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
editionfield as a legacy compatibility value that reportscommunity-poption are separated correctlyVerification
rg -n -i "enterprise edition|commercial Operaton|commercial offering|commercial product|community edition|license key|license-key|Get License Key|Set License Key|Delete License Key" docs src README.md docusaurus.config.ts package.jsonnow only returns historical Camunda 7 Community Edition release-note references, not Operaton edition or license-key wordinggit diff --checknpm run buildsucceeds; it reports the known pre-existing Docusaurus link/anchor warnings addressed by follow-up docs quality PRsReferences checked: