Update articles/healthcare-apis/azure-api-for-fhir/purge-history.md

Co-authored-by: Shelly Haverkamp <[email protected]>

Author: EXPEkesheth

articles/healthcare-apis/azure-api-for-fhir/purge-history.md

@@ -33,7 +33,7 @@ The `$purge-history` operation was created to help with the management of resour
 
 Since `$purge-history` is a resource level operation versus a type level or system level operation, you'll need to run the operation for every resource that you want remove the history from.
 
-By default, the purge history operation waits for successful completion before deleting resources. However, if any errors occur during the execution of the purge-history operation, the deletion of resources will be rolled back. To prevent this rollback behavior, you can use the optional query parameter ‘allowPartialSuccess’ and set it to true during the purge-history call. This ensures that the transaction will not be rolled back in case of an error.
+By default, the purge history operation waits for successful completion before deleting resources. However, if any errors occur during the execution of the purge-history operation, the deletion of resources is rolled back. To prevent this rollback behavior, use the optional query parameter ‘allowPartialSuccess’ and set it to true during the purge-history call. This step ensures that the transaction isn't rolled back in case of an error.
 
 ## Examples of purge history