Skip to content

Conversation

@YadingFang
Copy link
Contributor

What type of PR is this?

Add one of the following kinds:

  • documentation

What this PR does / why we need it:

  • Terminology: Replaced "customer" with "API consumer".
  • Capabilities: Added "Terminate call" and "Retrieve recording" to the feature list.
  • Cleanup: Removed application-level UI descriptions (web-based, clicking buttons, etc.) that are outside the API scope.

Special notes for reviewers:

Address documentation feedback from release review (PR #65).

@github-actions
Copy link

github-actions bot commented Feb 6, 2026

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 2 0 0.01s
✅ API spectral 1 0 1.78s
✅ GHERKIN gherkin-lint 3 0 1.08s
✅ REPOSITORY git_diff yes no 0.01s
✅ REPOSITORY secretlint yes no 0.74s
✅ YAML yamllint 1 0 0.49s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

…ndards

- Remove CloudEvent subject property from required attributes in API docs
- Remove application-level descriptions (masked numbers, privacy) from User Story
- Update examples to match CAMARA Commonalities standard
- Align with PR-B schema changes where subject was removed from YAML
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant