fixed warnings

Author: weslbo

learn-pr/wwl-databricks/implement-lakeflow-jobs/includes/2-create-lakeflow-job.md

@@ -46,7 +46,7 @@ Tasks that run code (notebooks, Python scripts, SQL files) need a source locatio
 
 **DBFS/ADLS** (for Python scripts) allows you to reference files stored in volumes or cloud storage. Provide the full URI, such as `abfss://[email protected]/path/script.py`.
 
-:::image type="content" source="../media/2-configure-lakeflow-task.png" alt-text="Screenshot of the lakeflow editor task configuration." lightbox="../media/2-configure-lakeflow-task":::
+:::image type="content" source="../media/2-configure-lakeflow-task.png" alt-text="Screenshot of the lakeflow editor task configuration." lightbox="../media/2-configure-lakeflow-task.png":::
 
 ## Configure compute resources
 

learn-pr/wwl-databricks/implement-lakeflow-jobs/includes/5-configure-job-alerts.md

@@ -50,7 +50,7 @@ To configure job-level notifications, follow these steps:
 6. Select the event types you want to trigger notifications: **Start**, **Success**, **Failure**, **Duration warning**, or **Streaming backlog**.
 7. Select **Save** when you finish adding notifications.
 
-:::image type="content" source="../media/5-create-job-notification" alt-text="Screenshot showing job notifications dialog." lightbox="../media/5-create-job-notification":::
+:::image type="content" source="../media/5-create-job-notification.png" alt-text="Screenshot showing job notifications dialog." lightbox="../media/5-create-job-notification.png":::
 
 Job-level notifications apply to the overall job run. However, job-level notifications aren't sent when individual tasks fail and retry. Consider this behavior when designing your notification strategy.