Fix grammar and technical terms in key concepts

[shamlasadikeen]

Purpose

Fix minor documentation issues in key-concepts.md to improve readability and technical accuracy.

Changes

• Fixed subject-verb agreement: 'belongs' to 'belong'
• Added proper hyphenation in technical term: 'JWT-formatted'

Documentation

This PR directly fixes documentation issues in key-concepts.md

Security checks

• Followed secure coding standards? yes
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes

Summary by CodeRabbit

• Documentation
  • Updated API Concepts documentation with improved formatting and punctuation for enhanced clarity and readability.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

Walkthrough

Updated typography and punctuation in the API Concepts documentation table, specifically refining the Access Token description from "JWT formatted self-contained access tokens" to "JWT-formatted, self-contained access tokens" with improved formatting and hyphenation.

Changes

Cohort / File(s)	Change Summary
Documentation Updates en/docs/get-started/key-concepts.md	Updated API Concepts table with refined typography and punctuation for the Access Token entry, adding hyphenation to "JWT-formatted" and commas for clarity.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Documentation-only change with purely typographical updates
• No logic, code, or structural modifications
• Single file affected with minimal scope

Suggested reviewers

• chamilaadhi
• tharikaGitHub

Poem

🐰 A comma here, a hyphen there,
Our docs now shine with polish rare!
JWT tokens stand so neat and bright,
Typography made just right!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete. While it addresses Purpose and some changes, most required template sections (Goals, Approach, User stories, Release note, Training, Certification, Marketing, Testing, Samples, Related PRs, Migrations, Test environment, and Learning) are missing or not properly filled.	Expand the description to include all applicable sections from the template, particularly Goals, Approach, Release note, and Testing details. For non-applicable sections, explicitly state 'N/A' with brief explanation.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely describes the main changes: fixing grammar (subject-verb agreement) and technical terms (JWT hyphenation) in the key concepts documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 37176a9 and c015f71.

📒 Files selected for processing (1)

• en/docs/get-started/key-concepts.md (1 hunks)

🔇 Additional comments (2)

en/docs/get-started/key-concepts.md (2)

10-10: Grammar fix is accurate.

Line 10 correctly changes "belongs" to "belong" since the subject "resources" is plural. The corrected subject-verb agreement improves the sentence clarity.

---

11-11: Hyphenation and punctuation improvements enhance readability.

Line 11 correctly hyphenates "JWT-formatted" as a compound adjective and adds a comma after it for improved punctuation. These changes enhance the technical accuracy and readability of the Access Token description.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}