diff --git a/src/modality-specific-files/magnetic-resonance-imaging-data.md b/src/modality-specific-files/magnetic-resonance-imaging-data.md
index 4db527fa35..9722b7824b 100644
--- a/src/modality-specific-files/magnetic-resonance-imaging-data.md
+++ b/src/modality-specific-files/magnetic-resonance-imaging-data.md
@@ -667,7 +667,7 @@ The definitions of these fields can be found in
 and a guide for using macros can be found at
  https://github.com/bids-standard/bids-specification/blob/master/macros_doc.md
 -->
-{{ MACROS___make_suffix_table(["ADC", "TRACE", "FA", "colFA"]) }}
+{{ MACROS___make_suffix_table(["adc", "trace", "fa", "colfa"]) }}
 
 <!--
 This block generates a filename templates.
@@ -696,9 +696,9 @@ In such a case, two files could have the following names:
 The user is free to choose any other label than `singleband` and
 `multiband`, as long as they are consistent across subjects and sessions.
 
-Scanner-generated TRACE, ADC and fractional anisotropy (FA and colFA) volumes MAY be included
-using the `TRACE`, `ADC`, `FA` and `colFA` suffixes, respectively.
-If TRACE, ADC, FA, or colFA volume filenames match a diffusion series with all applicable entities,
+Scanner-generated trace, ADC and fractional anisotropy (fa and colfa) volumes MAY be included
+using the `trace`, `adc`, `fa` and `colfa` suffixes, respectively.
+If trace, adc, fa, or colfa volume filenames match a diffusion series with all applicable entities,
 such volumes SHOULD be computed from that series.
 Otherwise, some entity, such as [`acq-<label>`](../appendices/entities.md#acq),
 SHOULD be used to indicate that the files are unrelated.