edits and markdown cleanup

Author: KendalBond007

articles/healthcare-apis/azure-api-for-fhir/azure-api-for-fhir-additional-settings.md

@@ -11,32 +11,32 @@ ms.date: 09/27/2023
 
 # Additional settings for Azure API for FHIR
 
-[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
+[!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 
-In this how-to guide, we'll review the additional settings you may want to set in your Azure API for FHIR. There are additional pages that drill into even more details.
+In this how-to guide, we review additional settings you may want to set in your Azure API for FHIR®.
 
 ## Configure Database settings
 
-Azure API for FHIR uses database to store its data. Performance of the underlying database depends on the number of Request Units (RU) selected during service provisioning or in database settings after the service has been provisioned.
+Azure API for FHIR uses a database to store its data. Performance of the underlying database depends on the number of Request Units (RU) selected during service provisioning, or in database settings after the service has been provisioned.
 
-Throughput must be provisioned to ensure that sufficient system resources are available for your database at all times. How many RUs you need for your application depends on operations you perform. Operations can range from simple read and writes to more complex queries.
+Throughput must be provisioned to ensure that sufficient system resources are always available for your database. How many RUs you need for your application depends on the operations you perform. Operations can range from simple read and writes to more complex queries.
 
 For more information on how to change the default settings, see [configure database settings](configure-database.md).
 
 ## Access control
 
-Azure API for FHIR will only allow authorized users to access the FHIR API. You can configure authorized users through two different mechanisms. The primary and recommended way to configure access control is using [Azure role-based access control (Azure RBAC)](../../role-based-access-control/index.yml), which is accessible through the **Access control (IAM)** blade. Azure RBAC only works if you want to secure data plane access using the Microsoft Entra tenant associated with your subscription. If you wish to use a different tenant, the Azure API for FHIR offers a local FHIR data plane access control mechanism. The configuration options aren't as rich when using the local RBAC mechanism. For details, choose one of the following options:
+Azure API for FHIR only allows authorized users to access the FHIR API. You can configure authorized users through two different mechanisms. The primary (and recommended) way to configure access control is using [Azure role-based access control (Azure RBAC)](../../role-based-access-control/index.yml), which is accessible through the **Access control (IAM)** blade. Azure RBAC only works if you want to secure data plane access using the Microsoft Entra tenant associated with your subscription. If you wish to use a different tenant, the Azure API for FHIR offers a local FHIR data plane access control mechanism. The configuration options aren't as rich when using the local RBAC mechanism. For details, choose one of the following options:
 
 * [Azure RBAC for FHIR data plane](configure-azure-rbac.md). This is the preferred option when you're using the Microsoft Entra tenant associated with your subscription.
 * [Local FHIR data plane access control](configure-local-rbac.md). Use this option only when you need to use an external Microsoft Entra tenant for data plane access control. 
 
 ## Enable diagnostic logging
-You may want to enable diagnostic logging as part of your setup to be able to monitor your service and have accurate reporting for compliance purposes. For details on how to set up diagnostic logging, see our [how-to-guide](enable-diagnostic-logging.md) on how to set up diagnostic logging, along with some sample queries. 
+You may want to enable diagnostic logging as part of your setup to be able to monitor your service and have accurate reporting for compliance purposes. For details on how to set up diagnostic logging, see our [how-to-guide](enable-diagnostic-logging.md), which also provides some sample queries. 
 
 ## Use custom headers to add data to audit logs
-In the Azure API for FHIR, you may want to include additional information in the logs, which comes from the calling system. To do including this information, you can use custom headers.
+In the Azure API for FHIR, you may want to include additional information in the logs, which comes from the calling system. To including this information, you can use custom headers.
 
-You can use custom headers to capture several types of information. For example:
+You can use custom headers to capture several types of information, including the following.
 
 * Identity or authorization information
 * Origin of the caller
@@ -54,4 +54,4 @@ Next check out the series of tutorials to create a web application that reads FH
 >[!div class="nextstepaction"]
 >[Deploy JavaScript application](tutorial-web-app-fhir-server.md)
 
-FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/azure-api-for-fhir/bulk-delete-operation.md

@@ -11,12 +11,12 @@ ms.author: kesheth
 
 # Bulk delete in Azure API for FHIR
 
-[!INCLUDE [bulk-delete operation common content](../includes/fhir-bulk-delete-operation.md)]
+[!INCLUDE[bulk-delete operation common content](../includes/fhir-bulk-delete-operation.md)]
 
 ## Related content
 
 [Supported FHIR features](fhir-features-supported.md)
 
 [FHIR REST API capabilities for Azure Health Data Services FHIR service](fhir-rest-api-capabilities.md)
 
-[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]