Update release-notes.md

EXPEkesheth · web-flow · commit bd09c1f11c5f · 2024-03-12T21:46:58.000-07:00
diff --git a/articles/healthcare-apis/azure-api-for-fhir/release-notes.md b/articles/healthcare-apis/azure-api-for-fhir/release-notes.md
@@ -22,12 +22,12 @@ Azure API for FHIR provides a fully managed deployment of the Microsoft FHIR Ser
 The query parameter _summary=count and _count=0 can be added to _history endpoint to get count of all versioned resources. This count includes soft deleted resources. For more information, see [history management](././../azure-api-for-fhir/purge-history.md).
 
 **Improve throughput for export operation**
-The "_isparallel" query parameter can be added to the export operation to enhance its throughput. It is important to note that using this parameter may result in an increase in Request Units consumption over the life of export. For more information, see [Export operation query parameters](././../azure-api-for-fhir/export-data.md).
+The "_isparallel" query parameter can be added to the export operation to enhance its throughput. Its' important to note that using this parameter may result in an increase in Request Units consumption over the life of export. For more information, see [Export operation query parameters](././../azure-api-for-fhir/export-data.md).
 > [!NOTE]
-> There is a known issue with the $export operation that could result in incomplete exports with status success. Issue occurs when the is_parallel flag was used. Export jobs executed with _isparallel query parameter starting February 13th, 2024 are impacted with this issue. 
+> There's a known issue with the $export operation that could result in incomplete exports with status success. Issue occurs when the is_parallel flag was used. Export jobs executed with _isparallel query parameter starting February 13th, 2024 are impacted with this issue. 
 
 **Change in name nomenclature for exported file name and default storage account**
-With this change, exported file names follow the format '{FHIR Resource Name}-{Number}-{Number}.ndjson'. The order of the files is not guaranteed to correspond to any ordering of the resources in the database. Default storage account name is updated to 'Export-{Number}'. There is no change to number of resources added in individual exported files. 
+With this change, exported file names follow the format '{FHIR Resource Name}-{Number}-{Number}.ndjson'. The order of the files isn't guaranteed to correspond to any ordering of the resources in the database. Default storage account name is updated to 'Export-{Number}'. There's no change to number of resources added in individual exported files. 
 
 
 **Performance Enhancement**
@@ -43,7 +43,7 @@ Conditional interactions can be complex and performance-intensive. To enhance th
 $export operation now supports exporting versioned resources and soft deleted resources. For more information, see [Export query parameters](../../healthcare-apis/azure-api-for-fhir/export-data.md).
 
 ## **November 2023**
-**Bulk delete capability now available**
+**Bulk delete capability now available in preview**
 `$bulk-delete' allows you to delete resources from FHIR server asynchronously. Bulk delete operation can be executed at system level or for individual resource type. For more information, see [bulk-delete operation](../../healthcare-apis/azure-api-for-fhir/bulk-delete-operation.md).
 
 Bulk delete operation is currently in public preview. Review disclaimer for details. [!INCLUDE public preview disclaimer]
@@ -67,7 +67,7 @@ For more details, visit [#3250](https://github.com/microsoft/fhir-server/pull/32
 ## **April 2023**
 
 **Fixed transient issues associated with loading custom search parameters**
-This bug fix address the issue, where the FHIR service would not load the latest SearchParameter status in event of failure.
+This bug fix addresses the issue, where the FHIR service wouldn't load the latest SearchParameter status in the event of failure.
 For more details, visit [#3222](https://github.com/microsoft/fhir-server/pull/3222)
 
 ## **November 2022**
@@ -82,7 +82,7 @@ Bug is now fixed and Resource will be updated if matches the Etag header. For de
 
 |Enhancement |Related information |
 | :----------------------------------- | :--------------- |
-|Azure API for FHIR does not create a new version of the resource if the resource content has not changed. |If a user updates an existing resource and only meta.versionId or meta.lastUpdated have changed then we return OK with existing resource information without updating VersionId and lastUpdated. For more information, see [#2519](https://github.com/microsoft/fhir-server/pull/2519). |
+|Azure API for FHIR doesn't create a new version of the resource if the resource content hasn't changed. |If a user updates an existing resource and only meta.versionId or meta.lastUpdated have changed then we return OK with existing resource information without updating VersionId and lastUpdated. For more information, see [#2519](https://github.com/microsoft/fhir-server/pull/2519). |
 
 ## April 2022
 
@@ -114,7 +114,7 @@ Bug is now fixed and Resource will be updated if matches the Etag header. For de
 |Bug fixes |Related information |
 | :----------------------------------- | :--------------- |
 |Duplicate resources in search with `_include` |Fixed issue where a single resource can be returned twice in a search that has `_include`. For more information, see [PR #2448](https://github.com/microsoft/fhir-server/pull/2448). |
-|PUT creates on versioned update |Fixed issue where creates with PUT resulted in an error when the versioning policy is configured to `versioned-update`. For more information, see [PR #2457](https://github.com/microsoft/fhir-server/pull/2457). |
+|PUT creates on versioned update |Fixed issue were creates with PUT resulted in an error when the versioning policy is configured to `versioned-update`. For more information, see [PR #2457](https://github.com/microsoft/fhir-server/pull/2457). |
 |Invalid header handling on versioned update |Fixed issue where invalid `if-match` header would result in an HTTP 500 error. Now an HTTP Bad Request is returned instead. For more information, see [PR #2467](https://github.com/microsoft/fhir-server/pull/2467). |
 
 ## February 2022
@@ -213,8 +213,8 @@ Bug is now fixed and Resource will be updated if matches the Etag header. For de
 
 |Custom search bugs |Related information |
 | :----------------------------------- | :--------------- |
-|Addresses the delete failure with Custom Search parameters. | [#2133](https://github.com/microsoft/fhir-server/pull/2133)|
-|Added retry logic while Deleting Search parameter. | [#2121](https://github.com/microsoft/fhir-server/pull/2121)|
+|Addresses failure with the custom search parameters. | [#2133](https://github.com/microsoft/fhir-server/pull/2133)|
+|Added retry logic while deleting search parameter. | [#2121](https://github.com/microsoft/fhir-server/pull/2121)|
 |Set max item count in search options in SearchParameterDefinitionManager. | [#2141](https://github.com/microsoft/fhir-server/pull/2141)|
 |Provides better exception if there's a bad expression in search parameter. |[#2157](https://github.com/microsoft/fhir-server/pull/2157)|
 
