fix

Author: bwren

articles/azure-monitor/logs/logs-ingestion-api-overview.md

@@ -16,7 +16,6 @@ The application sends data to a [data collection endpoint (DCE)](../essentials/d
 The data sent by your application to the API must be formatted in JSON and match the structure expected by the DCR. It doesn't necessarily need to match the structure of the target table because the DCR can include a [transformation](../essentials//data-collection-transformations.md) to convert the data to match the table's structure. You can modify the target table and workspace by modifying the DCR without any change to the API call or source data.
 
 :::image type="content" source="media/logs-ingestion-api-overview/overview-log-ingestion-api.png" lightbox="media/logs-ingestion-api-overview/overview-log-ingestion-api.png" alt-text="Diagram that shows an overview of logs ingestion API." border="false":::
-0945482d6aa37f96bc6c7eef2ea96deabc2854cd
 
 ## Configuration
 The following table describes each component in Azure that you must configure before you can use the Logs Ingestion API.