Improve the way enterprise functionality is described

[nortonandreev]

User description

Original PR: #5256

I saw that the cherry-pick command has failed, so creating this PR against v25.0 – have carried over the 24.10 tag and have added 25.1 too.

If the script fails again, I will manually open PRs against these two versions.

---

Pr ticket

{'summary': 'Improve enterprise features description and correct license documentation links\n', 'description': 'Description\n- The documentation contained outdated GitHub repository references pointing to the old EventStore organization instead of the current kurrent-io organization\n- Enterprise features description needed clarification to better communicate availability and licensing options\n- Documentation should include direct reference to enterprise editions information\n\nDeliverables\n- Update URLs: Correct all license documentation links to point to kurrent-io/KurrentDB repository\n- Enhance Description: Add hyperlink to enterprise editions page and improve wording clarity\n- Clarify Language: Change "only enabled" to "can be enabled" for more accurate feature availability messaging\n'}

---

PR Type

Documentation

---

Description

• Updated license URL references from EventStore to kurrent-io organization

• Improved enterprise features description with direct link to editions page

• Changed wording from "only enabled" to "can be enabled" for clarity

---

Diagram Walkthrough

flowchart LR
  A["License URL References"] -->|"Update to kurrent-io"| B["GitHub Links"]
  C["Enterprise Features Text"] -->|"Add editions link"| D["Enhanced Description"]
  E["Licensing Language"] -->|"Clarify availability"| F["Better Wording"]

Loading

File Walkthrough

Relevant files

Documentation

README.md Update license URLs and improve enterprise features wording docs/server/quick-start/README.md Updated GitHub license URL from EventStore/EventStore to kurrent-io/KurrentDB repository (2 occurrences) Added hyperlink to enterprise features page (https://www.kurrent.io/kurrent-platform-editions) Changed wording from "enterprise features are only enabled" to "enterprise features can be enabled" for improved clarity +2/-2

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
🟢	No codebase code duplication found No new components were introduced in the PR code
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

No code suggestions found for the PR.

[github-actions]

🚨 @nortonandreev Failed to create cherry Pick PR due to error:

RequestError [HttpError]: Merge conflict
   at /home/runner/work/_actions/kurrent-io/Automations/master/cherry-pick-pr-for-label/node_modules/@octokit/request/dist-node/index.js:66:23
   at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
 status: '409',
 headers: {
   'access-control-allow-origin': '*',
   'access-control-expose-headers': 'ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Resource, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, X-GitHub-SSO, X-GitHub-Request-Id, Deprecation, Sunset',
   'content-length': '127',
   'content-security-policy': "default-src 'none'",
   'content-type': 'application/json; charset=utf-8',
   date: 'Mon, 02 Feb 2026 11:28:06 GMT',
   'referrer-policy': 'origin-when-cross-origin, strict-origin-when-cross-origin',
   server: 'github.com',
   'strict-transport-security': 'max-age=31536000; includeSubdomains; preload',
   vary: 'Accept-Encoding, Accept, X-Requested-With',
   'x-accepted-github-permissions': 'contents=write',
   'x-content-type-options': 'nosniff',
   'x-frame-options': 'deny',
   'x-github-api-version-selected': '2022-11-28',
   'x-github-media-type': 'github.v3; format=json',
   'x-github-request-id': '2401:247BC6:1DEB36B:83D97CD:69808A45',
   'x-ratelimit-limit': '5000',
   'x-ratelimit-remaining': '4990',
   'x-ratelimit-reset': '1770035282',
   'x-ratelimit-resource': 'core',
   'x-ratelimit-used': '10',
   'x-xss-protection': '0'
 },
 request: {
   method: 'POST',
   url: 'https://api.github.com/repos/kurrent-io/KurrentDB/merges',
   headers: {
     accept: 'application/vnd.github.v3+json',
     'user-agent': 'octokit-core.js/3.3.2 Node.js/20.19.6 (linux; x64)',
     authorization: 'token [REDACTED]',
     'content-type': 'application/json; charset=utf-8'
   },
   body: '{"base":"cherry-pick-cherry-pick/5484/docs-enterprise-feature-wording-release/v24.10-96a80c01-9113-4c6b-af23-de0f3ffa93fe","commit_message":"Merge 7602160dbb3901949daa5cb91496ce5af447a0ca into cherry-pick-cherry-pick/5484/docs-enterprise-feature-wording-release/v24.10-96a80c01-9113-4c6b-af23-de0f3ffa93fe [skip ci]\\n\\n\\nskip-checks: true\\n","head":"7602160dbb3901949daa5cb91496ce5af447a0ca"}',
   request: { agent: [Agent], hook: [Function: bound bound register] }
 },
 documentation_url: 'https://docs.github.com/rest/branches/branches#merge-a-branch'
}

🚨👉 Check https://github.com/kurrent-io/KurrentDB/actions/runs/21588270424

[github-actions]

@nortonandreev 👉 Created pull request targeting release/v25.1: #5485