Update export-data.md

Author: EXPEkesheth

articles/healthcare-apis/azure-api-for-fhir/export-data.md

@@ -64,8 +64,8 @@ The Azure API for FHIR supports the following query parameters. All of these par
 | \_typefilter | Yes | To request finer-grained filtering, you can use \_typefilter along with the \_type parameter. The value of the _typeFilter parameter is a comma-separated list of FHIR queries that further restrict the results |
 | \_container | No |  Specifies the container within the configured storage account where the data should be exported. If a container is specified, the data will be exported into a folder into that container. If the container isn’t specified, the data will be exported to a new container. |
 | \_till | No |  Allows you to only export resources that have been modified till the time provided. This parameter is applicable to only System-Level export. In this case, if historical versions have not been disabled or purged, export guarantees true snapshot view, or, in other words, enables time travel. |
-|\_includeHistory | No | Allows you to export versioned resources. This filter does not work with '_typeFilter' query parameter. |
-|\_includeDeleted | No | Allows you to export soft deleted resources. To learn more about delete, refer to [delete using FHIR specification](https://www.hl7.org/fhir/http.html#delete). This filter does not work with '_typeFilter' query parameter. |
+|\_includeHistory | No | Allows you to export versioned resources. This filter does'nt work with '_typeFilter' query parameter. |
+|\_includeDeleted | No | Allows you to export soft deleted resources. To learn more about delete, refer to [delete using FHIR specification](https://www.hl7.org/fhir/http.html#delete). This filter does'nt work with '_typeFilter' query parameter. |
 
 > [!NOTE]
 > Only storage accounts in the same subscription as that for Azure API for FHIR are allowed to be registered as the destination for $export operations.