updates from build views

Author: KendalBond007

articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-fhir-server.md

@@ -12,7 +12,7 @@ ms.custom: devx-track-js
 
 ---
 
-# Deploy JavaScript app to read data from Azure API for FHIR
+# Deploy a JavaScript app to read data from Azure API for FHIR
 
 [!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 

articles/healthcare-apis/azure-api-for-fhir/tutorial-web-app-write-web-app.md

@@ -10,11 +10,11 @@ author: expekesheth
 ms.date: 09/27/2023
 ---
 
-# Write Azure web application to read FHIR data in Azure API for FHIR
+# Write an Azure web application to read FHIR data in Azure API for FHIR
 
 [!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 
-Now that you're able to connect to your FHIR® server and POST data, you’re ready to write a web application that will read FHIR data. In this final step of the tutorial, we walk through writing and accessing the web application.
+Once you're able to connect to your FHIR® server and POST data, you’re ready to write a web application that will read FHIR data. In this final step of the tutorial, we walk through writing and accessing the web application.
 
 ## Create web application
 In Azure, select **Create a resource** and select **Web App**. Make sure to name your web application whatever you specified in the redirect URI for your client application, or go back and update the redirect URI with the new name. 
@@ -23,7 +23,7 @@ In Azure, select **Create a resource** and select **Web App**. Make sure to name
 
 Once the web application is available, select **Go to resource**. Select **App Service Editor (Preview)** under Development Tools on the right and then select **Go**. Selecting **Go** opens up the App Service Editor. Right select in the grey space under *Explore* and create a new file called **index.html**.
 
-The following is the code that you can input into **index.html**. You’ll need to update the following items.
+The following is code you can input into **index.html**. You’ll need to update the following items.
 * **clientId** - Update with your client application ID. This ID is the same ID you pulled when retrieving your token
 * **authority** - Update with your Microsoft Entra tenant ID
 * **FHIRendpoint** - Update the FHIRendpoint to have your FHIR service name

articles/healthcare-apis/azure-api-for-fhir/validation-against-profiles.md

@@ -15,7 +15,7 @@ ms.author: kesheth
 
 In the [store profiles in Azure API for FHIR](store-profiles-in-fhir.md) article, you walked through the basics of FHIR profiles and storing them. This article guides you through how to use `$validate` for validating resources against profiles. Validating a resource against a profile means checking if the resource conforms to the profile, including the specifications listed in `Resource.meta.profile` or in an Implementation Guide (IG).
 
-`$validate` is an operation in Fast Healthcare Interoperability Resources (FHIR®) that allows you to ensure that a FHIR resource conforms to the base resource requirements or a specified profile. This operation ensures that the data in Azure API for FHIR  has the expected attributes and values. For information on validate operation, visit [HL7 FHIR Specification](https://www.hl7.org/fhir/resource-operation-validate.html). Per the specification, Mode can be specified with `$validate`, such as create and update.
+`$validate` is an operation in Fast Healthcare Interoperability Resources (FHIR®) that allows you to ensure that a FHIR resource conforms to the base resource requirements or a specified profile. This operation ensures that the data in Azure API for FHIR  has the expected attributes and values. For information on validate operation, visit the [HL7 FHIR Specification](https://www.hl7.org/fhir/resource-operation-validate.html). Per the specification, `Mode` (such as `create` and `update`) can be specified with `$validate`.
 
 - `create`: Azure API for FHIR checks that the profile content is unique from the existing resources and that it's acceptable to be created as a new resource.
 - `update`: Checks that the profile is an update against the nominated existing resource (that is no changes are made to the immutable fields).
@@ -26,10 +26,10 @@ There are different ways provided for you to validate resource.
 - Validate a new resource with validate operation.
 - Validate on resource CREATE/UPDATE using a header.
 
-Azure API for FHIR always returns an `OperationOutcome` as the validation results for `$validate` operation. Azure API for FHIR service does two step validation once a resource is passed into `$validate` endpoint. The first step is a basic validation to ensure resource can be parsed. During resource parsing, individual errors need to be fixed before proceeding to next step. Once a resource is successfully parsed, full validation is conducted as the second step.
+Azure API for FHIR always returns an `OperationOutcome` as the validation results for a `$validate` operation. Azure API for FHIR service does two step validation once a resource is passed into a `$validate` endpoint. The first step is a basic validation to ensure the resource can be parsed. During resource parsing, individual errors need to be fixed before proceeding to next step. Once a resource is successfully parsed, full validation is conducted as the second step.
 
 > [!NOTE]
-> Any `Valuesets` that are to be used for validation must be uploaded to the FHIR server. This includes any `Valuesets` which are part of the FHIR specification, as well as any `ValueSets` defined in Implementation Guides. Only fully expanded `Valuesets`, which contain a full list of all codes are supported. Any `ValueSet` definitions which reference external sources are not supported.
+> Any `Valuesets` that are to be used for validation must be uploaded to the FHIR server. This includes any `Valuesets` which are part of the FHIR specification, as well as any `ValueSets` defined in Implementation Guides. Only fully expanded `Valuesets` which contain a full list of all codes are supported. Any `ValueSet` definitions which reference external sources are not supported.
 
 ## Validating an existing resource
 
@@ -55,7 +55,7 @@ In this example, you're validating the existing Patient resource `a6e11662-def8-
     ]
 }
 ```
-If the resource isn't valid, you get an error code and an error message with details on why the resource is invalid. An example `OperationOutcome` gets returned with error messages and could look like the following code example.
+If the resource isn't valid, you get an error code and an error message with details on why the resource is invalid. An `OperationOutcome` gets returned with error messages, and could look like the following code example.
 
 ```json
 {
@@ -116,7 +116,7 @@ For example,
 
 This request validates the resource. Resources aren't created in FHIR service on validation. You need to send a POST request without `$validate` to create a resource.
 
-## Validate on resource CREATE/ UPDATE using header.
+## Validate on a resource CREATE/UPDATE using a header
 
 By default, Azure API for FHIR is configured to opt out of validation on resource `Create/Update`. This capability allows validation on `Create/Update`, using the `x-ms-profile-validation` header. Set `x-ms-profile-validation` to true for validation.