Address CodeRabbit review comments: typos, grammar, and phrasing improvements

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: nirmal070125

en/docs/data-transformation/guides/hl7v2-fhir.md

@@ -220,11 +220,11 @@ The service processes incoming POST requests containing HL7v2 messages. When a m
 
 Let's look into the the detailed implementation of this. Let's assume the [custom-service-openapi.yaml](../references/custom-service-openapi.yaml) is inside the resources folder. 
 
-1. Generate the files using openapi files as below. 
+1. Generate the files from the OpenAPI file as follows.
 ```bash
 bal openapi -i resources/custom-service-openapi.yaml --mode service -o <OUTPUT-FOLDER>
 ```
-2. The types.bal file is auto generated to the specified folder and it does not need any changes to be done. 
+2. The types.bal file is auto-generated into the specified folder and does not require any changes.
 3. Update the custom-service-openapi-service.bal file as below. 
 ```ballerina
 // AUTO-GENERATED FILE.

en/docs/fhir/guides/connecting-ehr-emr-systems.md

@@ -19,7 +19,7 @@ Follow the instructions given below to set up the connectors you require in your
 </ul>
 
 ## Install the connector
-As mentioned in the previous section, WSO2 Integration Studio is the IDE that will be used to develop integrations that will be deployed in the integration layer of the Healthcare solution. The connector zip that is obtained from WSO2 should be imported to the Integration Studio in order to develop the integration flow.<br /> Steps on installing and using the connector can be found by clicking the [link](https://apim.docs.wso2.com/en/4.0.0/reference/connectors/connectors-overview/#how-to-use-connectors)<br />
+As mentioned in the previous section, WSO2 Integration Studio is the IDE that will be used to develop integrations that will be deployed in the integration layer of the Healthcare solution. The connector zip that is obtained from WSO2 should be imported to the Integration Studio in order to develop the integration flow.<br /> Steps on installing and using the connector can be found in the [connector usage guide](https://apim.docs.wso2.com/en/4.0.0/reference/connectors/connectors-overview/#how-to-use-connectors)<br />
 
 ## Connect system to integration logic
 In this section let’s walk through a simple example of connecting to the Epic EHR system and searching and retrieving some patient data. Epic is a FHIR compliant EHR system. WSO2 has a pre-built connector for the Epic sandbox environment. Let’s create a new Integration project and add a Rest API to it. More information on creating the integration project,and the Rest API can be found [here](https://apim.docs.wso2.com/en/4.0.0/integrate/develop/integration-development-kickstart/).<br />Then let's import the Epic connector to the Integration Studio as mentioned in the previous section. Once imported the mediator <strong>Palette</strong> of the Integration Studio will have the Epic connector listed. As shown in the below image:

en/docs/fhir/guides/expose-fhir-apis.md

@@ -58,8 +58,8 @@ Once the required FHIR resources have been exposed as FHIR APIs, the server is r
 To learn more about RESTful FHIR, refer to the [official FHIR documentation](https://www.hl7.org/fhir/http.html).
 
 - Interactions
-    - Instance level - All the instance level interactions are pre-templated in the API definitions of the WSO2 FHIR API Hub. Relevant backend integration logic has to be implemented by the developer. (A project skeleton with boilerplate code will be provided to speed up the deployment.)
-    - Type level - Type level interactions are also handled in a similar manner as in Instance level interactions.
+    - Instance-level - All the instance-level interactions are pre-templated in the API definitions of the WSO2 FHIR API Hub. Relevant backend integration logic has to be implemented by the developer. (A project skeleton with boilerplate code will be provided to speed up the deployment.)
+    - Type level - Type-level interactions are also handled in a similar manner as in instance-level interactions.
     - System level - Only Capabilities interaction is available as a default feature.
 - Capability statement
     - This document describes the server's meta information so that the stakeholders can query and decide whether the server supports expected operation/interaction. This includes all the implemented FHIR resource APIs, search parameters of each FHIR resource, supported interactions and expected payload structures etc.

en/docs/fhir/guides/populating-fhir-resources.md

@@ -28,7 +28,7 @@ Before you begin, ensure you have <a href="https://ballerina.io/downloads/instal
 2. Import the required modules to the Ballerina program. In this sample we are using FHIR Patient resource from international base FHIR IG. Therefore, we need to import `ballerinax/health.fhir.r4.international401` package. If you are using a different IG of FHIR, you can import the relevant package from the [central](https://central.ballerina.io/search?q=fhir&page=1&m=packages) or generated from the bal [health tool](https://ballerina.io/learn/health-tool/#package-generation).
 
     ```ballerina
-    import ballerinax/health.fhir.r4.internationa401;
+    import ballerinax/health.fhir.r4.international401;
     import ballerina/io;
     ```
 3. Create a custom patient record type to represent the patient data. In this sample, the patient record contains the patient's first name, last name, address, and phone number.

en/docs/get-started/architecture.md

@@ -39,7 +39,7 @@ These FHIR templates are auto-generated from FHIR specification, and we can gene
 
 #### FHIR API Definitions
 
-FHIR defines a RESTful API interface to any [FHIR resource](https://hl7.org/fhir/http.html). We built another tool to automatically generate the Open API Specification 3.0 based API definition files for any FHIR profile or an implementation guide. These API definitions can be imported to the API designer of WSO2 in order to expose respective FHIR APIs.
+FHIR defines a RESTful API to any [FHIR resource](https://hl7.org/fhir/http.html). We built another tool to automatically generate the OpenAPI Specification 3.0-based API definition files for any FHIR profile or an implementation guide. These API definitions can be imported to the API designer of WSO2 in order to expose respective FHIR APIs.
 
 #### Security and Privacy
 

en/docs/get-started/introduction.md

@@ -1,12 +1,12 @@
 ---
 sidebar_position: 2
 title: "Introduction"
-description: The WSO2 Open Healthcare is a solution built on top of the best in its industry, that has been an open-source integration platform.
+description: WSO2 Open Healthcare is a solution built on top of the industry-leading open-source integration platform.
 ---
 
 
 
-The WSO2 Open Healthcare is a solution built on top of the best in its industry, that has been an open-source integration platform. The platform allows you to connect to disparate source systems (e.g., EHRs/EMRs, Claim Management Systems, Databases etc.), quickly transforming your data to/from healthcare message formats (e.g., FHIR, HL7, X12, CCDA etc.) and expose them through secure APIs.<br /> Our main intent is to accelerate the development process of healthcare IT through auto generative, easily extensible and well supported set of healthcare accelerators.
+WSO2 Open Healthcare is a solution built on top of the industry-leading open-source integration platform. The platform allows you to connect to disparate source systems (e.g., EHRs/EMRs, Claim Management Systems, Databases etc.), quickly transforming your data to/from healthcare message formats (e.g., FHIR, HL7, X12, CCDA etc.) and expose them through secure APIs.<br /> Our main intent is to accelerate the development process of healthcare IT through auto generative, easily extensible and well supported set of healthcare accelerators.
 
 ![Healthcare Solution Offering](/assets/img/get-started/healthcare-solution-offering.png)
 

en/docs/install-and-setup/updates/overview.md

@@ -12,8 +12,7 @@ With updates, you do not have to wait until the next product version release to
 Read more about [WSO2 latest update tool](https://updates.docs.wso2.com/en/latest/updates/overview/).
 
 ## How to get WSO2 updates?
-A subscription is mandatory to get WSO2 updates. A Subscription can be obtained by different ways and there are different
-types of subscription tiers available.
+A subscription is required to receive WSO2 updates. Subscriptions are available in different tiers to suit your requirements.
 
 Read more about [WSO2 subscription model](https://updates.docs.wso2.com/en/latest/updates/overview/#how-to-get-wso2-updates)
 

en/docs/install-and-setup/updates/update-accelerators.md

@@ -7,9 +7,9 @@ description: Usually Healthcare accelerators are the implementation which accele
 # How to update Healthcare solution?
 
 Usually Healthcare accelerators are the implementation which accelerate and facilitate the FHIR related features, these accelerators will be applied on top of 
-the wso2 base products like APIM and MI in order to cater the healthcare domain problems.
+the WSO2 base products (such as APIM and MI) to address healthcare domain requirements.
 
-In order to get updates for Healthcare solution we need to get the update for two separate products as below,
+To get updates for the Healthcare solution we need to get the update for two separate products as below,
 
 * Download the GA/ Vanilla pack of the wso2 base products like APIM or MI.
 * Update the base products to the latest/ desired update level.

en/docs/secure-health-apis/guides/configure-smart-on-fhir.md

@@ -97,4 +97,4 @@ curl --location --request POST 'https://localhost:9443/oauth2/token?grant_type=a
 --header 'Authorization: Basic <base64>(CONSUMER_KEY:CONSUMER_SECRET)'
 ```
 5. You will get the access_token along with the id_token. 
-6. By decoding the id_token you will be able to retrieve the Patient Id that we assigned to user 'johndoe'. 
+6. By decoding the id_token, you will be able to retrieve the Patient ID that we assigned to the user 'johndoe'.