Update check.md

docs/check.md

@@ -72,12 +72,12 @@ In this schema, the output needs to match the format with the variables defined
 
 ![Screenshot 2023-09-27 at 12 32 31 PM](https://github.com/model-driven-devops/mdd-base/assets/65776483/654fcf8a-05ba-46eb-88df-d59220517608)
 
-One you commit your change, the pipeline will run and you will see our hq-pop router failed the check because we haven't actually configured our device yet.
+Once you commit your change, the pipeline will run and you will see our hq-pop router failed the check because we haven't actually configured our device yet.
 
-![Screenshot 2023-09-27 at 12 33 33 PM](https://github.com/model-driven-devops/mdd-base/assets/65776483/249cd617-345f-4fa2-b698-db9882a49c3f)
+![Screenshot 2023-09-27 at 2 49 27 PM](https://github.com/model-driven-devops/mdd-base/assets/65776483/076157e5-b1c5-431c-9536-3bb4bb6039a5)
 
 ## Configure Netflow
-Now that we have our test written to check for an approved netflow configuration, let's create the config file. Navigate to your web IDE and open your mdd-data directory. Select "Create a new file" and title it "oc-netflow.yml".
+Now that we have our test written to check for an approved netflow configuration, let's create the config file. Navigate to your web IDE and open your mdd-data directory using the same branch created for your check file. Select "Create a new file" and title it "oc-netflow.yml".
 
 ![Screenshot 2023-09-27 at 12 36 38 PM](https://github.com/model-driven-devops/mdd-base/assets/65776483/ffb36f90-0c62-4914-b937-d7ad5d9eb925)
 
@@ -108,6 +108,7 @@ The "mdd_tags" field at the top of the config denotes that we only want this con
 
 Once you implement your changes, commit to your existing branch. You will end up with a successful CI run because our hq-pop router now has the correct netflow configuration applied. 
 
+![Screenshot 2023-09-27 at 2 52 10 PM](https://github.com/model-driven-devops/mdd-base/assets/65776483/aa3ef02b-6ae1-42cd-90b4-02694c7eb4ef)