Refactor text for clarity in key concepts documentation

[Yathunanthanasarma]

Rephrase sentences for improved clarity and readability.

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to certification@wso2.com and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

• Unit tests

  Code coverage information

• Integration tests

  Details about the test cases and coverage

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
• Ran FindSecurityBugs plugin and verified report? yes/no
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e6700c7b-6d77-48cd-a300-2be923147260

📥 Commits

Reviewing files that changed from the base of the PR and between 71a2d45 and bb11937.

📒 Files selected for processing (1)

• en/docs/get-started/key-concepts.md

---

📝 Walkthrough

Summary

This PR improves clarity in the key concepts documentation by refactoring text throughout the "Message entry points" and related sections.

Changes

Updated en/docs/get-started/key-concepts.md with the following refinements:

• Rephrased definitions for APIs, Proxy Services, and Inbound Endpoints for improved clarity
• Made editorial adjustments to the Mediators definition
• Reworded the Connectors description with grammar improvements
• Revised the Scheduled triggers and Transports paragraphs with clearer wording and formatting

All changes are text-focused refinements without structural or heading modifications. This is a low-effort documentation improvement (7 lines changed).

Walkthrough

This pull request contains editorial refinements to the key-concepts documentation for WSO2 Micro Integrator. The changes reword concept definitions for message entry points (APIs, Proxy Services, Inbound Endpoints), mediators, connectors, scheduled triggers, and transports. All modifications preserve the underlying semantic content and reference structure while improving clarity and grammatical consistency. No structural, heading, or code-level changes are introduced.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description uses the required template structure but nearly all substantive sections are left unfilled with only placeholder text, providing minimal actionable information about purpose, goals, approach, or impact.	Complete the key sections: explicitly state the clarity improvements made, confirm documentation-only impact, and provide details on testing, certification, and marketing implications.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: rephrasing documentation text for improved clarity, which aligns with the file modifications shown in the raw summary.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}