diff --git a/docs/running_the_software.md b/docs/running_the_software.md
index 0880f98..f4ff077 100644
--- a/docs/running_the_software.md
+++ b/docs/running_the_software.md
@@ -2,14 +2,7 @@
## Input data in BIDS standard
-The input dataset must be organized according to the [BIDS data structure](https://bids.neuroimaging.io/){cite}`Gorgolewski2016-zm`. RABIES will iterate through subjects and search for all available functional scans with suffix 'bold'. Anatomical scans are not necessary (`--bold_only` runs preprocessing with only functional scans), but can improve registration quality. If anatomical scans are used for preprocessing, each functional scan will be matched to one corresponding anatomical scan with suffix `T1w` or `T2w` of the same subject/session. Extra files which don't have a functional or structural suffix will be ignored.
-
-
-Mandatory BIDS specifications are:
-* `sub-{subject ID}` and `ses-{session ID}` for both functional and anatomical images
-* `bold` suffix for functional images
-* `T1w` or `T2w` for anatomical images
-* `run-{run #}` is necessary for functional images if there are multiple scans per session
+The input dataset must be organized according to the [BIDS data structure](https://bids.neuroimaging.io/){cite}`Gorgolewski2016-zm`. RABIES will iterate through all subjects found to contain a functional file (see section on BIDS filters below), and will also iterate according to sessions and runs found within each subject if available. If anatomical scans are used for preprocessing (i.e. not using `--bold_only`), each functional scan will be matched to one corresponding anatomical scan of the same subject/session (using BIDS filters for the anatomical image, see below).
### Directory structure for an example dataset
* Our [example dataset](http://doi.org/10.5281/zenodo.8349029) has the following BIDS structure:
@@ -68,6 +61,19 @@ Mandatory BIDS specifications are: