Skip to content

Fix typos and grammar errors across documentation - #55

Merged
sameeragunarathne merged 2 commits into
wso2:mainfrom
nirmal070125:fix/typos-and-grammar
May 21, 2026
Merged

Fix typos and grammar errors across documentation#55
sameeragunarathne merged 2 commits into
wso2:mainfrom
nirmal070125:fix/typos-and-grammar

Conversation

@nirmal070125

Copy link
Copy Markdown
Contributor

Summary

  • Scanned all 79 Markdown files under en/docs/
  • Fixed 45 typos and grammar errors across 21 files
  • No changes to code blocks, URLs, product names, or technical terms

Types of fixes

  • Misspelled words (e.g. ReceipientsRecipients, AccelaratorAccelerator, BallrinaBallerina, crendetialscredentials)
  • Grammar errors (subject-verb disagreement, missing articles, wrong prepositions)
  • Punctuation and phrasing issues

Files changed

File Issues Fixed
get-started/introduction.md 3
get-started/architecture.md 3
configurations/email-notification.md 2
data-transformation/guides/hl7v2-fhir.md 2
fhir/guides/connecting-ehr-emr-systems.md 4
fhir/guides/expose-fhir-apis.md 3
fhir/guides/exposing-an-api.md 1
fhir/guides/fhir-repository-connector.md 4
fhir/guides/metadata-api.md 3
fhir/guides/parsing-and-serializing.md 1
fhir/guides/populating-fhir-resources.md 2
fhir/guides/profiles-and-extensions.md 1
fhir/guides/smart-api.md 1
hl7/guides/overview.md 1
hl7/guides/populating-hl7-message.md 1
install-and-setup/manual.md 1
install-and-setup/updates/overview.md 3
install-and-setup/updates/update-accelerators.md 2
secure-health-apis/guides/configure-smart-on-fhir.md 6
secure-health-apis/guides/smart-on-fhir-overview.md 1
advance-topics/guides/enable-workflow.md 2

🤖 Generated with Claude Code

@coderabbitai

coderabbitai Bot commented May 21, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Rate limit exceeded

@nirmal070125 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 56 minutes and 29 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 957490ce-81cc-4fa9-bca4-b473c0f9f42b

📥 Commits

Reviewing files that changed from the base of the PR and between ae7fbc1 and e7c5989.

📒 Files selected for processing (21)
  • en/docs/advance-topics/guides/enable-workflow.md
  • en/docs/configurations/email-notification.md
  • en/docs/data-transformation/guides/hl7v2-fhir.md
  • en/docs/fhir/guides/connecting-ehr-emr-systems.md
  • en/docs/fhir/guides/expose-fhir-apis.md
  • en/docs/fhir/guides/exposing-an-api.md
  • en/docs/fhir/guides/fhir-repository-connector.md
  • en/docs/fhir/guides/metadata-api.md
  • en/docs/fhir/guides/parsing-and-serializing.md
  • en/docs/fhir/guides/populating-fhir-resources.md
  • en/docs/fhir/guides/profiles-and-extensions.md
  • en/docs/fhir/guides/smart-api.md
  • en/docs/get-started/architecture.md
  • en/docs/get-started/introduction.md
  • en/docs/hl7/guides/overview.md
  • en/docs/hl7/guides/populating-hl7-message.md
  • en/docs/install-and-setup/manual.md
  • en/docs/install-and-setup/updates/overview.md
  • en/docs/install-and-setup/updates/update-accelerators.md
  • en/docs/secure-health-apis/guides/configure-smart-on-fhir.md
  • en/docs/secure-health-apis/guides/smart-on-fhir-overview.md
📝 Walkthrough

Walkthrough

This pull request consolidates 42 documentation fixes across the healthcare accelerator guides under the en/docs/ directory. A new TYPO_AND_GRAMMAR_REPORT.md file documents all corrections, which address typos, grammatical errors, spelling inconsistencies, and formatting issues. Changes span FHIR API guides, HL7 documentation, installation and setup instructions, secure API guides, and general getting-started content. No code or configuration changes are included.

Suggested reviewers

  • isuruh15
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Fix typos and grammar errors across documentation' directly and accurately summarizes the main objective of the pull request.
Description check ✅ Passed The description provides a comprehensive overview of the changes, including the scope (79 Markdown files scanned), number of fixes (45 typos/grammar errors across 21 files), types of corrections made, and a detailed table of affected files.
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

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 10

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
en/docs/fhir/guides/populating-fhir-resources.md (1)

28-32: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Fix the Ballerina FHIR package import typo in the guide snippet.

Line ~28 references ballerinax/health.fhir.r4.international401, but the code block at line ~31 imports ballerinax/health.fhir.r4.internationa401 (missing l). Update the import in the snippet to ballerinax/health.fhir.r4.international401.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@en/docs/fhir/guides/populating-fhir-resources.md` around lines 28 - 32, The
code snippet import has a typo: change the package import in the fenced
Ballerina snippet from "ballerinax/health.fhir.r4.internationa401" to the
correct "ballerinax/health.fhir.r4.international401" so it matches the intended
FHIR IG package name referenced in the text; update the import line in the
snippet accordingly.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@en/docs/data-transformation/guides/hl7v2-fhir.md`:
- Around line 223-227: Rewrite the two sentences for clarity and hyphenation:
change "openapi files as below" to "the OpenAPI file below" and "auto generated"
to "auto-generated", so the first line reads like "Generate the files using the
OpenAPI file below:" (keeping the bal CLI invocation "bal openapi -i
resources/custom-service-openapi.yaml --mode service -o <OUTPUT-FOLDER>") and
the second line reads like "The types.bal file is auto-generated into the
specified folder and does not require any changes." Ensure consistent
capitalization of "OpenAPI" and keep references to the bal command and types.bal
unchanged.

In `@en/docs/fhir/guides/connecting-ehr-emr-systems.md`:
- Around line 21-22: The markdown link text "[link]" under the "Install the
connector" section is too generic—replace it with a descriptive label such as
"WSO2 connector usage guide" (or similar) so readers know what the link points
to; update the inline markdown link where "[link]" appears to use the new
descriptive text while keeping the same URL and surrounding punctuation.

In `@en/docs/fhir/guides/expose-fhir-apis.md`:
- Line 61: Change the un-hyphenated compound modifier "Instance level" to
"Instance-level" and any occurrences of "instance level interactions" to
"instance-level interactions" in the sentence that reads "Instance level - All
the instance level interactions are pre-templated..." so the phrasing becomes
"Instance-level - All the instance-level interactions are pre-templated..." to
ensure consistent compound-modifier hyphenation.

In `@en/docs/get-started/architecture.md`:
- Line 42: Update the sentence that currently reads "FHIR defines a RESTful API
interface to any FHIR resource" to remove the redundant word "interface" and
hyphenate "3.0 based" to "3.0-based"; specifically change the phrase to
something like "FHIR defines a RESTful API to any FHIR resource. We built
another tool to automatically generate the OpenAPI Specification 3.0-based API
definition files for any FHIR profile or an implementation guide." Target the
sentence containing "FHIR defines a RESTful API interface to any FHIR resource"
and the phrase "Open API Specification 3.0 based API definition files" for these
edits.

In `@en/docs/get-started/introduction.md`:
- Line 4: The frontmatter "description" value and the opening sentence in the
body are grammatically incorrect and unclear; update both to a concise, clear
sentence such as: "WSO2 Open Healthcare is an open-source integration platform
for healthcare systems." Replace the existing frontmatter description and the
corresponding opening sentence in the document body with this wording (look for
the frontmatter key description and the document's first paragraph/opening
sentence).

In `@en/docs/install-and-setup/updates/overview.md`:
- Around line 15-16: The two sentences shown ("A subscription is mandatory to
get WSO2 updates." and "A Subscription can be obtained by different ways and
there are different types of subscription tiers available.") are awkward and
redundant—replace them with a concise, consistent phrasing such as: "A
subscription is required to receive WSO2 updates; subscriptions are available in
multiple tiers and can be obtained in several ways." Apply the same clarity and
consistency to the similar text at the other occurrences (lines referenced 22-23
and 26) so all subscription guidance uses the same concise wording and
capitalization.

In `@en/docs/install-and-setup/updates/update-accelerators.md`:
- Around line 10-12: Rewrite the two introductory sentences for grammar and
clarity: replace "the wso2 base products like APIM and MI in order to cater the
healthcare domain problems." with a concise sentence such as "These updates
apply to WSO2 base products, including APIM and MI, to support healthcare domain
requirements." and replace "In order to get updates for Healthcare solution we
need to get the update for two separate products as below," with something like
"To obtain Healthcare solution updates, install the updates for the two separate
products listed below:" — update the exact phrases shown ("the wso2 base
products like APIM and MI..." and "In order to get updates for Healthcare
solution...") accordingly to match tone and grammar across the document.

In `@en/docs/secure-health-apis/guides/configure-smart-on-fhir.md`:
- Line 100: The phrase "Patient Id" in the sentence starting "By decoding the
id_token you will be able to retrieve the Patient Id that we assigned to user
'johndoe'." uses inconsistent capitalization; change "Patient Id" to "Patient
ID" to match the rest of the guide and standard acronym casing, updating that
exact sentence text accordingly.

In `@TYPO_AND_GRAMMAR_REPORT.md`:
- Line 121: Item 10's summary text incorrectly states "four headings" while
listing five heading labels; update the item so the count and list match by
either changing the count to "five headings" or removing one of the listed
labels (`#Connecting`, `##Overview`, `##Set up`, `##Install`, `##Connect`) to
leave four entries—ensure the item text and the bullet/list are consistent
(refer to item 10 and the listed heading labels).
- Around line 6-61: The report's top metadata ("Total issues fixed:"), the Index
Table header counts, and the detailed numbered entries are inconsistent (showing
42, 48, and 45); update them to a single consistent total and matching
one-to-one numbering. Inspect the "Total issues fixed:" value, the Index Table
rows beginning with "| # | File | Issue Type | Summary |", and the detailed list
of numbered items (entries 1–48) and either remove the 3 extra index entries or
add the 3 missing detailed entries so the count matches (choose a single
canonical total and apply it across the "Total issues fixed:" line, the index
table numbering, and the detailed issue list). Ensure numbering, counts, and
summaries are aligned and consistent throughout the document.

---

Outside diff comments:
In `@en/docs/fhir/guides/populating-fhir-resources.md`:
- Around line 28-32: The code snippet import has a typo: change the package
import in the fenced Ballerina snippet from
"ballerinax/health.fhir.r4.internationa401" to the correct
"ballerinax/health.fhir.r4.international401" so it matches the intended FHIR IG
package name referenced in the text; update the import line in the snippet
accordingly.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b8626e80-b1cc-47f1-bcd8-8c4856766cbb

📥 Commits

Reviewing files that changed from the base of the PR and between 1e373cb and 7f50983.

📒 Files selected for processing (22)
  • TYPO_AND_GRAMMAR_REPORT.md
  • en/docs/advance-topics/guides/enable-workflow.md
  • en/docs/configurations/email-notification.md
  • en/docs/data-transformation/guides/hl7v2-fhir.md
  • en/docs/fhir/guides/connecting-ehr-emr-systems.md
  • en/docs/fhir/guides/expose-fhir-apis.md
  • en/docs/fhir/guides/exposing-an-api.md
  • en/docs/fhir/guides/fhir-repository-connector.md
  • en/docs/fhir/guides/metadata-api.md
  • en/docs/fhir/guides/parsing-and-serializing.md
  • en/docs/fhir/guides/populating-fhir-resources.md
  • en/docs/fhir/guides/profiles-and-extensions.md
  • en/docs/fhir/guides/smart-api.md
  • en/docs/get-started/architecture.md
  • en/docs/get-started/introduction.md
  • en/docs/hl7/guides/overview.md
  • en/docs/hl7/guides/populating-hl7-message.md
  • en/docs/install-and-setup/manual.md
  • en/docs/install-and-setup/updates/overview.md
  • en/docs/install-and-setup/updates/update-accelerators.md
  • en/docs/secure-health-apis/guides/configure-smart-on-fhir.md
  • en/docs/secure-health-apis/guides/smart-on-fhir-overview.md

Comment thread en/docs/data-transformation/guides/hl7v2-fhir.md Outdated
Comment thread en/docs/fhir/guides/connecting-ehr-emr-systems.md Outdated
Comment thread en/docs/fhir/guides/expose-fhir-apis.md Outdated
Comment thread en/docs/get-started/architecture.md Outdated
Comment thread en/docs/get-started/introduction.md Outdated
Comment thread en/docs/install-and-setup/updates/overview.md Outdated
Comment thread en/docs/install-and-setup/updates/update-accelerators.md Outdated
Comment thread en/docs/secure-health-apis/guides/configure-smart-on-fhir.md Outdated
Comment thread TYPO_AND_GRAMMAR_REPORT.md Outdated
Comment thread TYPO_AND_GRAMMAR_REPORT.md Outdated

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@en/docs/fhir/guides/expose-fhir-apis.md`:
- Line 62: Replace the awkward phrase "in a similar manner as in instance-level
interactions" in the sentence starting "Type level - Type-level interactions..."
with a clearer construction such as "similarly to instance-level interactions"
so the full line reads "Type level - Type-level interactions are handled
similarly to instance-level interactions." Ensure only the phrasing changes and
preserve the existing meaning and punctuation around "Type level - Type-level
interactions."

In `@en/docs/get-started/introduction.md`:
- Line 9: Replace the unhyphenated compound modifier "auto generative" with the
hyphenated form "auto-generative" in the introduction paragraph (the sentence
referencing "auto generative, easily extensible and well supported set of
healthcare accelerators") so the compound modifier before "set of healthcare
accelerators" is grammatically correct and consistent.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 58b45b9d-9c14-47d5-a35e-7fe9451d3d6f

📥 Commits

Reviewing files that changed from the base of the PR and between 7f50983 and ae7fbc1.

📒 Files selected for processing (9)
  • en/docs/data-transformation/guides/hl7v2-fhir.md
  • en/docs/fhir/guides/connecting-ehr-emr-systems.md
  • en/docs/fhir/guides/expose-fhir-apis.md
  • en/docs/fhir/guides/populating-fhir-resources.md
  • en/docs/get-started/architecture.md
  • en/docs/get-started/introduction.md
  • en/docs/install-and-setup/updates/overview.md
  • en/docs/install-and-setup/updates/update-accelerators.md
  • en/docs/secure-health-apis/guides/configure-smart-on-fhir.md
✅ Files skipped from review due to trivial changes (5)
  • en/docs/install-and-setup/updates/update-accelerators.md
  • en/docs/install-and-setup/updates/overview.md
  • en/docs/data-transformation/guides/hl7v2-fhir.md
  • en/docs/fhir/guides/populating-fhir-resources.md
  • en/docs/secure-health-apis/guides/configure-smart-on-fhir.md

Comment thread en/docs/fhir/guides/expose-fhir-apis.md
Comment thread en/docs/get-started/introduction.md
nirmal070125 and others added 2 commits May 21, 2026 17:04
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ovements

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@nirmal070125
nirmal070125 force-pushed the fix/typos-and-grammar branch from ae7fbc1 to e7c5989 Compare May 21, 2026 11:35
@sameeragunarathne
sameeragunarathne merged commit 44509c1 into wso2:main May 21, 2026
3 checks passed
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.

2 participants