Merge pull request #8368 from MicrosoftDocs/JasonHQX-patch-3

Update azure-synapse-link-advanced-configuration.md

Author: Mattp123

powerapps-docs/maker/data-platform/azure-synapse-link-advanced-configuration.md

@@ -46,7 +46,7 @@ The table below describes how rows are handled in the lake against CUD events fo
 |---------|---------|---------|
 |Create     |  The row is inserted in the partition file and is based on the `createdOn` value on the row.       | The row is added to the end of the partition file and is based on the `createdOn` value of the record.    |
 |Update     | If the row exists in the partition file, then it's replaced or updated with updated data. If it doesn't exist, it's inserted in the file.    |  The row, along with the updated version, is added to the end of the partition file.   |
-|Delete     |  If the row exists in the partition file, it's removed from the file.    | The row is added to the end of the partition file with `isDeleted column = True`.    |
+|Delete     |  If the row exists in the partition file, it's removed from the file.    | The row is added to the end of the partition file with `IsDelete column = True`.    |
 
 > [!NOTE]
 > For Dataverse tables where **Append only** is enabled, deleting a row in the source will not delete or remove the row in the lake. Instead, the deleted row is appended as a new row in the lake and the `isDeleted` column is set to **True**.