Added note about Alignment QC batch mode vs skip step trigger

docs/pipeline/automation/dragen_alignment_qc.md

@@ -7,9 +7,7 @@ _(See [automated_pipeline.svg](../../model/automated_pipeline.svg))_
 
 - See [metadata.md](../metadata.md) note for NTC/PTC sample treatment.
 - With Portal Ocicat release, the workflow does not differentiate between WGS or WTS. Hence, "DRAGEN Alignment QC".
-- We run DRAGEN Alignment QC at per "lane" level per sequencing run for WGS library.
-- WTS tumor library are typically single lane.  
-
+- We run DRAGEN Alignment QC at "lane" level for each WGS/WTS library.
 
 ## Option 1
 
@@ -18,6 +16,10 @@ _Step 1)_
   - _Attached [dragen_alignment_qc.json](dragen_alignment_qc.json) here for convenience_
 - The `batch_run_id` attribute is optional.
 
+> NOTE:
+> 
+> This will resume pipeline automation in "batch mode by sequencing run context" i.e. **it will trigger all downstream workflows**. In some scenario, you might want to skip some specific orchestration steps induced by QC complete. This use case is possible through leveraging `step_skip_list` system parameter. See `Pipeline Control > Step Skip` in [README](./README.md).
+
 _Step 2)_
 - Find corresponding `SequenceRun` info from `/sequencerun` endpoint
 ```bash
@@ -42,8 +44,3 @@ aws lambda invoke \
   --payload file://dragen_alignment_qc.json \
   out.json
 ```
-
-
-## Option 2
-
-_Meanwhile, please ask for orchestrator batch trigger option availability in Slack `#data-portal`._