Update export-data.md

Author: EXPEkesheth

articles/healthcare-apis/fhir/export-data.md

@@ -66,8 +66,8 @@ The FHIR service supports the following query parameters for filtering exported
 | `_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 limit the results. |
 | `_container` | No |  Specifies the name of the container in the configured storage account where the data should be exported. If a container is specified, the data will be exported into a folder in that container. If the container isn't specified, the data will be exported to a new container with an autogenerated name. |
 | `_till` | No |  Allows you to export resources that have been modified till the specified time. This parameter is applicable only with 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 sepcification](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 the FHIR service are allowed to be registered as the destination for `$export` operations.