Not sure any of these changes actually took - VSC weird

Author: KendalBond007

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

@@ -21,7 +21,7 @@ Azure API for FHIR® provides a fully managed deployment of the Microsoft FHI
 
 **Date Search Logic Update**: When searching for a date, the logic now ensures that any date range containing the searched date is included in the results. Previously, it only matched a date if the entire range was inside the searched date.
 
-**Health Checks for Improved Resiliency**: Added health checks to enhance the resilience of the service such as retriable exceptions, enhanced diagnostic logging and catching time out exceptions.
+**Health Checks for Improved Resiliency**: Added health checks to enhance the resilience of the service such as retriable exceptions, enhanced diagnostic logging, and catching time out exceptions.
 
 ## January 2025
 
@@ -33,7 +33,7 @@ Azure API for FHIR® provides a fully managed deployment of the Microsoft FHI
 
 **Transaction Failure Exception**: A new FHIR-specific exception type has been introduced to handle Cosmos DB transaction failures, replacing the generic `InvalidOperationExceptions`.
 
-**CMK Error Handling**: Improved error handling for operations dependent on customer-managed keys. Users will now see a more specific error message and a link to [Microsoft's troubleshooting guide](../fhir/configure-customer-managed-keys.md) if issues occur related to CMK.
+**CMK Error Handling**: Improved error handling for operations dependent on customer-managed keys. Users now see a more specific error message and a link to [Microsoft's troubleshooting guide](../fhir/configure-customer-managed-keys.md) if issues occur related to CMK.
 
 ## Related content
 

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

@@ -19,13 +19,13 @@ This article describes features, enhancements, and bug fixes released in 2025 fo
 
 **Selectable Search Parameters**: Customers can tune search parameters using the [selectable search parameters](./fhir/selectable-search-parameters.md) capability. The capability provides a `$status` endpoint to validate the status of the search parameter. To avoid conflicts, the change now prevents updates to the search parameter status when a reindex job is in progress.
 
-**Schema Upgrade Changes**: To improve customer experience during schema upgrades, the service now ensures that instances are initialized up to the minimum supported schema version. If a schema upgrade is in progress, the service will continue to respond while initializing the instance in parallel.
+**Schema Upgrade Changes**: To improve customer experience during schema upgrades, the service now ensures that instances are initialized up to the minimum supported schema version. If a schema upgrade is in progress, the service continues to respond while initializing the instance in parallel.
 
 **Incremental Import Enhancement**: Error handling has been added for `lastUpdated` input values marked in the future during ingestion using the import operation. The error handling includes a check to ensure that if the input `lastUpdated` is set to less than 10 seconds in the future, the input resources with dates in the future are rejected.
 
 **Date Search Logic Update**: When searching for a date, the logic now ensures that any date range containing the searched date is included in the results. Previously, it only matched a date if the entire range was inside the searched date.
 
-**Health Checks for Improved Resiliency**: Added health checks to enhance the resilience of the service such as retriable exceptions, enhanced diagnostic logging and catching time out exceptions.
+**Health Checks for Improved Resiliency**: Added health checks to enhance the resilience of the service such as retriable exceptions, enhanced diagnostic logging, and catching time out exceptions.
 
 ## January 2025
 
@@ -36,15 +36,15 @@ This article describes features, enhancements, and bug fixes released in 2025 fo
 **HTTP Method Validation for Transaction Bundle Requests**:
 Added validation to ensure the HTTP method in the Request component of the transaction bundle is a valid HTTPVerb enum value. If the HTTP method is invalid or null, a `RequestNotValidException` is thrown with a `400 Bad Request` status, providing a clearer error message to users.
 
-**CMK Error Handling**: Improved error handling for operations dependent on customer-managed keys. Users will now see a more specific error message and a link to [Microsoft's troubleshooting guide](fhir/configure-customer-managed-keys.md) if issues occur related to CMK.
+**CMK Error Handling**: Improved error handling for operations dependent on customer-managed keys. Users now see a more specific error message and a link to [Microsoft's troubleshooting guide](fhir/configure-customer-managed-keys.md) if issues occur related to CMK.
 
 #### 100 items limit on include and revinclude searches
 
-The FHIR® server has a limit of 100 items on `include` and `revinclude` searches. A recent update fixed an issue where this limit was not being applied in specific conditions. Customers will receive a warning and truncated results if the limit is exceeded. Details on limits can be found in the [Overview of FHIR search](./fhir/overview-of-search.md#search-result-parameters). To manage this, use the `_count` parameter to reduce the number of returned results. In the short term, we plan to increase the limit to 1000
+The FHIR® server has a limit of 100 items on `include` and `revinclude` searches. A recent update fixed an issue where this limit wasn't being applied in specific conditions. Customers will receive a warning and truncated results if the limit is exceeded. Details on limits can be found in the [Overview of FHIR search](./fhir/overview-of-search.md#search-result-parameters). To manage this, use the `_count` parameter to reduce the number of returned results. In the short term, we plan to increase the limit to 1000
 
 ### Bug Fixes
 
-**Billing in Sweden Central region**: An issue was discovered where subscriptions in the Sweden Central region were not being billed correctly. We corrected the error, and billing has now been enabled in Sweden Central region. If you were affected by this error, you will not be responsible for any missed charged prior to your January bill.
+**Billing in Sweden Central region**: An issue was discovered where subscriptions in the Sweden Central region weren't being billed correctly. We corrected the error, and billing has now been enabled in Sweden Central region. If you were affected by this error, you won't be responsible for any missed charges prior to your January bill.
 
 ## Related content