toc consistency fix

Author: shellyhaverkamp

articles/healthcare-apis/azure-api-for-fhir/toc.yml

@@ -125,9 +125,9 @@
       href: tutorial-member-match.md
     - name: Patient/$everything
       href: patient-everything.md
-    - name: $purge-history operation
+    - name: $purge-history
       href: purge-history.md
-    - name: bulk-delete operation
+    - name: $bulk-delete
       href: bulk-delete-operation.md
     - name: $validate
       expanded: false

articles/healthcare-apis/fhir/toc.yml

@@ -111,9 +111,9 @@ items:
       href: tutorial-member-match.md
     - name: Patient/$everything
       href: patient-everything.md
-    - name: $purge-history operation
+    - name: $purge-history
       href: purge-history.md
-    - name: $bulk-delete operation
+    - name: $bulk-delete
       href: fhir-bulk-delete.md
     - name: $validate
       items: 

articles/healthcare-apis/includes/fhir-bulk-delete-operation.md

@@ -120,5 +120,5 @@ Here's a list of error messages that might occur if the `$bulk-delete` operation
   When you run a `$bulk-delete` operation, you might see increased latency on concurrent calls to the service. To avoid a latency increase, we recommend that you cancel the `$bulk-delete` job, and then rerun it during a period of lower traffic.
 
 > [!NOTE]
-> If you cancel and then restart a `$bulk-delete` operation, it resumes the deletion process from where it previously stopped.
+> If you cancel and then restart a `$bulk-delete` operation, the deletion process resumes from where it was stopped.