Merge pull request #125098 from ArieHein/Spelling-Wave-24

Spelling FIxes

Author: v-dirichards

articles/healthcare-apis/azure-api-for-fhir/how-to-run-a-reindex.md

@@ -107,7 +107,7 @@ content-type: application/fhir+json
 "parameter": [
     {
       "name": "targetSearchParameterTypes",
-      "valueString": "{url of custom search parameter. In case of multiple custom search parameters, url list can be comma seperated.}"
+      "valueString": "{url of custom search parameter. In case of multiple custom search parameters, url list can be comma separated.}"
     }
 ] 
 

articles/healthcare-apis/azure-api-for-fhir/register-service-azure-ad-client-app.md

@@ -38,7 +38,7 @@ Follow these steps to create a new service client.
 Permissions for Azure API for FHIR are managed through role-based access control (RBAC). For more details, visit [Configure Azure RBAC for FHIR](configure-azure-rbac.md).
 
 >[!NOTE]
->Use a `grant_type` of `client_credentials` when trying to otain an access token for Azure API for FHIR using tools such as Postman. For more details, visit [Testing the FHIR API on Azure API for FHIR](tutorial-web-app-test-postman.md).
+>Use a `grant_type` of `client_credentials` when trying to obtain an access token for Azure API for FHIR using tools such as Postman. For more details, visit [Testing the FHIR API on Azure API for FHIR](tutorial-web-app-test-postman.md).
 
 ## Application secret
 

articles/healthcare-apis/azure-api-for-fhir/release-notes.md

@@ -205,7 +205,7 @@ Bug is now fixed and Resource will be updated if it matches the Etag header. For
 
 |Enhancements |Related information |
 | :------------------- | :--------------- |
-|Added Publisher to `CapabiilityStatement.name` |You can now find the publisher in the capability statement at `CapabilityStatement.name`. [#2319](https://github.com/microsoft/fhir-server/pull/2319) |
+|Added Publisher to `CapabilityStatement.name` |You can now find the publisher in the capability statement at `CapabilityStatement.name`. [#2319](https://github.com/microsoft/fhir-server/pull/2319) |
 |Log `FhirOperation` linked to anonymous calls to Request metrics |We weren’t logging operations that didn’t require authentication. We extended the ability to get `FhirOperation` type in `RequestMetrics` for anonymous calls. [#2295](https://github.com/microsoft/fhir-server/pull/2295) |
 
 ### **Bug fixes**

articles/healthcare-apis/configure-private-link.md

@@ -52,7 +52,7 @@ For the resource type, search and select **Microsoft.HealthcareApis/workspaces**
 
 ### Manual approval
 
-For manual approval, select the second option under Resource, **Connect to an Azure resource by resource ID or alias**. For the resource ID, enter **subscriptions/{subcriptionid}/resourceGroups/{resourcegroupname}/providers/Microsoft.HealthcareApis/workspaces/{workspacename}**. For the Target subresource, enter **healthcareworkspace** as in Auto Approval.
+For manual approval, select the second option under Resource, **Connect to an Azure resource by resource ID or alias**. For the resource ID, enter **subscriptions/{subscriptionid}/resourceGroups/{resourcegroupname}/providers/Microsoft.HealthcareApis/workspaces/{workspacename}**. For the Target subresource, enter **healthcareworkspace** as in Auto Approval.
 
 :::image type="content" source="media/private-link/private-link-resource-id.png" alt-text="Screen image of the Manual Approval Resources tab.":::
 

articles/healthcare-apis/dicom/dicom-services-conformance-statement-v2.md

@@ -124,7 +124,7 @@ If an attribute is padded with nulls, the attribute is indexed when searchable a
 | `500 (Internal Server Error)`  | The server encountered an unknown internal error. Try again later.                                                                                                                                                 |
 | `503 (Service Unavailable)`    | The service is unavailable or busy. Try again later.                                                                                                                                                               |
 
-### Store response paylo
+### Store response payload
 
 The response payload populates a DICOM dataset with the following elements:
 

articles/healthcare-apis/fhir/azure-ad-b2c-setup.md

@@ -53,7 +53,7 @@ New-AzResourceGroupDeployment -ResourceGroupName $resourcegroupname -TemplateUri
 
 1. Use `Connect-AzAccount` to sign in to Azure. After you sign in, use `az account show --output table` to verify the subscription and tenant you want to use. Change the subscription and tenant if needed.
 
-1. Create a new resource group (or use an existing one) by skipping the "create reource group" step or commenting out the line starting with `az group create`.
+1. Create a new resource group (or use an existing one) by skipping the "create resource group" step or commenting out the line starting with `az group create`.
 
 ```bash
 ### variables

articles/healthcare-apis/fhir/convert-data-configuration.md

@@ -185,7 +185,7 @@ There are many methods for securing ACR using the built-in firewall depending on
 * [Configure rules to access an Azure container registry behind a firewall](/azure/container-registry/container-registry-firewall-access-rules)
 * [Azure IP Ranges and Service Tags – Public Cloud](https://www.microsoft.com/download/details.aspx?id=56519)
 
-<!-- * [Allow trusted services to securely access a network-restricted container registry](/azure/container-registry/allow-access-trusted-services)  This link should follow the Restric access link (currently 3rd from bottom).-->
+<!-- * [Allow trusted services to securely access a network-restricted container registry](/azure/container-registry/allow-access-trusted-services)  This link should follow the Restrict access link (currently 3rd from bottom).-->
 
 <!-- Removed from document per ADO131844, can be un-commented when service updates (similar for above link)
 > [!NOTE]

articles/healthcare-apis/fhir/fhir-service-resource-manager-template.md

@@ -261,7 +261,7 @@ az deployment group create --resource-group $resourcegroupname --template-file '
 
 ## Review the deployed resources
 
-You can verify that the FHIR service is up and running by opening a browser and navigating to `https://<yourfhir servic>.azurehealthcareapis.com/metadata`. If the capability statement is displayed or downloaded automatically, your deployment is successful. 
+You can verify that the FHIR service is up and running by opening a browser and navigating to `https://<yourfhir service>.azurehealthcareapis.com/metadata`. If the capability statement is displayed or downloaded automatically, your deployment is successful. 
 
 ## Clean up the resources
 

articles/healthcare-apis/release-notes-2021.md

@@ -51,7 +51,7 @@ We started the process of providing PowerShell, CLI scripts, and ARM templates t
 
 #### Process patient-everything links
 
-We expanded the atient-everything capabilities to process patient links [PR #2305](https://github.com/microsoft/fhir-server/pull/2305). For more information, see [Patient-everything in FHIR](./../healthcare-apis/fhir/patient-everything.md#processing-patient-links).
+We expanded the patient-everything capabilities to process patient links [PR #2305](https://github.com/microsoft/fhir-server/pull/2305). For more information, see [Patient-everything in FHIR](./../healthcare-apis/fhir/patient-everything.md#processing-patient-links).
 
 ### Bug fixes