fix

Author: likebupt

articles/machine-learning/how-to-deploy-pipelines.md

@@ -63,9 +63,9 @@ Once you have a pipeline up and running, you can publish a pipeline so that it r
         version="1.0")
    ```
 
-4. After publish your pipeline, you can check it in UI. Pipeline ID is the unique identified of thie published pipeline.
+4. After you publish your pipeline, you can check it in UI. Pipeline ID is the unique identified of thie published pipeline.
 
- ![published pipeline detail](./media/how-to-create-your-first-pipeline/published-pipeline-detail.png)
+    :::image type="content" source="./media/how-to-deploy-pipelines/published-pipeline-detail.png" alt-text="Screenshot showing published pipeline detail." lightbox= "./media/how-to-deploy-pipelines/published-pipeline-detail.png":::
 
 ## Run a published pipeline
 

articles/machine-learning/how-to-use-pipeline-ui.md

@@ -89,11 +89,10 @@ If your pipeline fails or gets stuck on a node, first view the logs.
 
     The **system_logs folder** contains logs generated by Azure Machine Learning. Learn more about [how to view and download log files for a run](how-to-log-view-metrics.md#view-and-download-log-files-for-a-run).
 
-    :::image type="content" source="./media/how-to-use-pipeline-ui/view-user-log.png" alt-text="Screenshot showing the user logs of a node." lightbox= "./media/how-to-use-pipeline-ui/check-logs.gif":::
+    ![How to check node logs](media/how-to-use-pipeline-ui/node-logs.gif)
 
     If you don't see those folders, this is due to the compute run time update isn't released to the compute cluster yet, and you can look at **70_driver_log.txt** under **azureml-logs** folder first.
 
-    :::image type="content" source="./media/how-to-use-pipeline-ui/view-driver-logs.png" alt-text="Screenshot showing the driver logs of a node." lightbox= "./media/how-to-use-pipeline-ui/view-driver-logs.png":::
 
 ## Clone a pipeline job to continue editing