minor content changes

Author: kpeechara

articles/azure-monitor/containers/container-insights-logs-schema.md

@@ -65,7 +65,7 @@ Kubernetes Metadata and Logs Filtering enhances the ContainerLogsV2 schema with
 - **Customized include list configuration:**  Users can tailor new metadata fields they want to see through editing the [configmap](https://github.com/microsoft/Docker-Provider/blob/ci_prod/kubernetes/container-azm-ms-agentconfig.yaml). Note that all metadata fields are collected by default when the `metadata_collection` is enabled and if you want to select specific fields, uncomment `include_fields` and specify the fields that need to be collected.
 
 <!-- convertborder later -->
-:::image type="content" source="./media/container-insights-logging-v2/configmap-list-config" lightbox="./media/container-insights-logging-v2/configmap-list-config.png" alt-text="Screenshot that shows metadata fields." border="false":::
+:::image type="content" source="./media/container-insights-logging-v2/configmap-list-config.png" lightbox="./media/container-insights-logging-v2/configmap-list-config.png" alt-text="Screenshot that shows metadata fields." border="false":::
 
 - **Enhanced ContainerLogV2 schema with log level:** Users can now assess application health based on color coded severity levels such as CRITICAL, ERROR, WARNING, INFO, DEBUG, TRACE, or UNKNOWN. It’s a crucial tool for incident response and proactive monitoring. By visually distinguishing severity levels, users can quickly pinpoint affected resources. The color-coded system streamlines the investigation process and allows users to drill down even further by selecting the panel for an explore experience for further debugging. However, it’s important to note that this functionality is only applicable when using Grafana. If you’re using Log Analytics Workspace, the LogLevel is simply another column in the ContainerLogV2 table.