Add clarity for using looper check

docs/looper/how-to/rerun.md

@@ -34,8 +34,23 @@ currentPipestatManager.set_status(record_identifier="sample2", status_identifier
 ```
 More info on setting status can be found [here](../developer-tutorial/developer-pipestat.md#setting-and-checking-status).
 
+Now that your pipeline is setting statuses, you can check the status of all samples using:
+```shell
+looper check
+```
+This command will show you a list of samples and their associated status,e.g:
+
+```
+     'count_lines' pipeline status summary     
+┏━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
+┃    Status     ┃    Jobs count/total jobs    ┃
+┡━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
+│   completed   │             1/3             │
+│    failed     │             2/3             │
+└───────────────┴─────────────────────────────┘
+```
 
-Now that your pipeline is setting statuses, you can resubmit failed jobs with:
+You can resubmit all failed jobs with:
 ```shell
 looper rerun
 ```

mkdocs.yml

@@ -153,7 +153,7 @@ nav:
         - Running project-level pipelines: looper/how-to/project-level-pipelines.md
         - Link similar results: looper/how-to/link-objects.md
         - Report objects:  looper/how-to/report-objects.md
-        - Rerun samples: looper/how-to/rerun.md
+        - Check status and rerun samples: looper/how-to/rerun.md
     - Pipeline Developer Docs:
       - Developer tutorial:
         - Writing a pipeline interface: looper/developer-tutorial/writing-a-pipeline-interface.md