Improve readability of intro sentence.

[Thisun-17]

Purpose

This PR fixes an issue where the initial description in the documentation included unclear phrasing. The sentence “simplifies your digital transformation journey” has now been split into two clearer statements to improve readability and flow.

Goals

The goal of this update is to improve clarity and make the documentation easier for users to understand by restructuring the sentence.

Approach

I updated the text in the relevant documentation file by rewriting the sentence into two separate lines. No UI changes were made.
Example fix applied:

• Original: “simplifies your digital transformation journey”
• Updated: Two clearer sentences to improve readability.

User stories

N/A — This change only updates documentation and does not affect user-facing functionality.

Release note

Improved clarity in documentation by restructuring unclear phrasing in the introductory sentence.

Documentation

Documentation updated in the same PR. No additional doc impact.

Training

N/A — This change does not affect training materials.

Certification

N/A — Documentation wording change does not impact certification content.

Marketing

N/A — Not a feature addition or product improvement requiring marketing content.

Automation tests

• Unit tests: N/A (documentation-only change)
• Integration tests: N/A

Security checks

• Followed secure coding standards? Yes
• Ran FindSecurityBugs? N/A (documentation change)
• Confirmed no secrets are committed? Yes

Samples

N/A — No samples were updated.

Related Public Relations

None.

Migrations (if applicable)

N/A: There is no effect of migration.

Test environment

Documentation-only change; no environment testing required.

Learning

Reviewed existing documentation patterns to ensure consistency with WSO2 writing standards.

Summary by CodeRabbit

• Documentation
  • Updated documentation with refined wording for improved clarity and readability.
  • Enhanced message structure with streamlined organization to make information more accessible.
  • Improved content presentation for better comprehension and engagement.

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

[coderabbitai]

Walkthrough

Documentation content in the hero/description section was rephrased for conciseness and readability. The first paragraph was split into a shorter opening sentence and now includes a "digital-transformation" term. No functional or logic changes.

Changes

Cohort / File(s)	Summary
Documentation Content Update en/docs/index.md	Rephrased hero/description text for improved clarity and conciseness; split opening paragraph and incorporated hyphenated "digital-transformation" terminology

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Single file modification
• Content-only changes (no code logic affected)
• Text rephrasing for readability—verify tone and terminology alignment with brand guidelines

Poem

🐰 The docs now sparkle, cleaner than before,
With words arranged to clarify and soar,
Digital transformation takes its stance,
A hero's tale enhanced at first glance! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Improve readability of intro sentence' directly and accurately reflects the main change: improving documentation readability by rewriting the introductory sentence.
Description check	✅ Passed	The description follows the required template structure and includes all major sections (Purpose, Goals, Approach, User stories, Release note, Documentation, Training, Certification, Marketing, Automation tests, Security checks, Samples, Related PRs, Migrations, Test environment, Learning) with appropriate content or N/A designations where applicable.
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

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

en/docs/index.md (1)

63-63: Great improvement to readability—consider removing redundant phrasing.

The rewrite successfully splits the introductory sentence into shorter, clearer statements, which improves flow and readability. The hyphenation of "digital-transformation" is also appropriate for the compound adjective usage.

However, the phrase "streamlines connectivity among applications, services, data, and the cloud" appears in both the second and third sentences, creating unnecessary repetition. Consider consolidating or rephrasing the third sentence to avoid this redundancy and maintain the clarity gain.

Suggested refinement:

-WSO2 Integrator: MI is a comprehensive integration solution. It simplifies your digital-transformation journey by streamlining connectivity among applications, services, data, and the cloud. The WSO2 Integrator: MI streamlines connectivity among applications, services, data, and the cloud using a user-friendly, low-code graphical design experience. Deployment options include both microservices and ESB styles for greater flexibility.
+WSO2 Integrator: MI is a comprehensive integration solution. It simplifies your digital-transformation journey by streamlining connectivity among applications, services, data, and the cloud. With a user-friendly, low-code graphical design experience, it supports both microservices and ESB styles for greater flexibility.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3311c74 and cc1c748.

📒 Files selected for processing (1)

• en/docs/index.md (1 hunks)