From 55265d48f3ea567cac5437bc448d55a29421cbc0 Mon Sep 17 00:00:00 2001
From: Dimitri Papadopoulos
 <3234522+DimitriPapadopoulos@users.noreply.github.com>
Date: Thu, 18 Nov 2021 06:40:22 +0100
Subject: [PATCH] Repeated words

---
 src/02-common-principles.md                                   | 2 +-
 .../01-magnetic-resonance-imaging-data.md                     | 2 +-
 src/04-modality-specific-files/02-magnetoencephalography.md   | 2 +-
 src/04-modality-specific-files/03-electroencephalography.md   | 2 +-
 src/99-appendices/08-coordinate-systems.md                    | 4 ++--
 src/schema/objects/entities.yaml                              | 2 +-
 src/schema/objects/suffixes.yaml                              | 2 +-
 7 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/src/02-common-principles.md b/src/02-common-principles.md
index 72323978c5..9975c948e4 100644
--- a/src/02-common-principles.md
+++ b/src/02-common-principles.md
@@ -118,7 +118,7 @@ misunderstanding we clarify them here.
     the final `_`), right before the **File extension**, for example, it is `eeg` in
     `sub-05_task-matchingpennies_eeg.vhdr`.
 
-1.  **File extension** - a portion of the the file name after the left-most
+1.  **File extension** - a portion of the file name after the left-most
     period (`.`) preceded by any other alphanumeric. For example, `.gitignore` does
     not have a file extension, but the file extension of `test.nii.gz` is `.nii.gz`.
     Note that the left-most period is included in the file extension.
diff --git a/src/04-modality-specific-files/01-magnetic-resonance-imaging-data.md b/src/04-modality-specific-files/01-magnetic-resonance-imaging-data.md
index 87b2fb42f7..ca1ce0fb33 100644
--- a/src/04-modality-specific-files/01-magnetic-resonance-imaging-data.md
+++ b/src/04-modality-specific-files/01-magnetic-resonance-imaging-data.md
@@ -234,7 +234,7 @@ The OPTIONAL [`acq-<label>`](../99-appendices/09-entities.md#acq)
 key/value pair corresponds to a custom label the user
 MAY use to distinguish a different set of parameters used for acquiring the same
 modality. For example this should be used when a study includes two T1w images -
-one full brain low resolution and and one restricted field of view but high
+one full brain low resolution and one restricted field of view but high
 resolution. In such case two files could have the following names:
 `sub-01_acq-highres_T1w.nii.gz` and `sub-01_acq-lowres_T1w.nii.gz`, however the
 user is free to choose any other label than `highres` and `lowres` as long as
diff --git a/src/04-modality-specific-files/02-magnetoencephalography.md b/src/04-modality-specific-files/02-magnetoencephalography.md
index 46a0841597..9d2e9cea07 100644
--- a/src/04-modality-specific-files/02-magnetoencephalography.md
+++ b/src/04-modality-specific-files/02-magnetoencephalography.md
@@ -211,7 +211,7 @@ Date time information MUST be expressed as indicated in [Units](../02-common-pri
 {{ MACROS___make_filename_template(datatypes=["meg"], suffixes=["channels"]) }}
 
 This file is RECOMMENDED as it provides easily searchable information across
-BIDS datasets for for example, general curation, response to queries or batch
+BIDS datasets for example, general curation, response to queries or batch
 analysis.
 To avoid confusion, the channels SHOULD be listed in the order they
 appear in the MEG data file.
diff --git a/src/04-modality-specific-files/03-electroencephalography.md b/src/04-modality-specific-files/03-electroencephalography.md
index 1222db4453..95070fca51 100644
--- a/src/04-modality-specific-files/03-electroencephalography.md
+++ b/src/04-modality-specific-files/03-electroencephalography.md
@@ -197,7 +197,7 @@ Date time information MUST be expressed as indicated in [Units](../02-common-pri
 {{ MACROS___make_filename_template(datatypes=["eeg"], suffixes=["channels"]) }}
 
 This file is RECOMMENDED as it provides easily searchable information across
-BIDS datasets for for example, general curation, response to queries or batch
+BIDS datasets for example, general curation, response to queries or batch
 analysis.
 To avoid confusion, the channels SHOULD be listed in the order they
 appear in the EEG data file.
diff --git a/src/99-appendices/08-coordinate-systems.md b/src/99-appendices/08-coordinate-systems.md
index 1b589da4d0..6a22162d3e 100644
--- a/src/99-appendices/08-coordinate-systems.md
+++ b/src/99-appendices/08-coordinate-systems.md
@@ -53,7 +53,7 @@ information for a coordinate system (origin and orientation) are specified in
 `<CoordSysType>CoordinateSystem`.
 The third piece of information for a coordinate system (units) are specified in
 `<CoordSysType>CoordinateUnits`.
-Here, `<CoordSysType>` can be one of of the following,
+Here, `<CoordSysType>` can be one of the following,
 depending on the data that is supposed to be documented:
 
 -   `MEG`
@@ -174,7 +174,7 @@ Restricted keywords for the `<CoordSysType>CoordinateSystem` field in the
 
 -   `ScanRAS`: The origin of the coordinate system is the center of the
     gradient coil for the corresponding T1w image of the subject, and the x-axis
-    increases left to right, the y-axis increases posterior to to anterior and
+    increases left to right, the y-axis increases posterior to anterior and
     the z-axis increases inferior to superior. For more information see the
     [Nipy Documentation](https://nipy.org/nibabel/coordinate_systems.html). It is
     strongly encouraged to align the subject's T1w to ACPC so that the `ACPC`
diff --git a/src/schema/objects/entities.yaml b/src/schema/objects/entities.yaml
index b5d4339d68..c1c8d5ed95 100644
--- a/src/schema/objects/entities.yaml
+++ b/src/schema/objects/entities.yaml
@@ -11,7 +11,7 @@ acquisition:
     user MAY use to distinguish a different set of parameters used for
     acquiring the same modality.
     For example this should be used when a study includes two T1w images - one
-    full brain low resolution and and one restricted field of view but high
+    full brain low resolution and one restricted field of view but high
     resolution.
     In such case two files could have the following names:
     `sub-01_acq-highres_T1w.nii.gz` and `sub-01_acq-lowres_T1w.nii.gz`, however
diff --git a/src/schema/objects/suffixes.yaml b/src/schema/objects/suffixes.yaml
index de492e5a1f..7449da2470 100644
--- a/src/schema/objects/suffixes.yaml
+++ b/src/schema/objects/suffixes.yaml
@@ -356,7 +356,7 @@ UNIT1:
     Note that although this image is T1-weighted, regions without MR signal will
     contain white salt-and-pepper noise that most segmentation algorithms will
     fail on.
-    Therefore, it is important to dissociate it from from `T1w`.
+    Therefore, it is important to dissociate it from `T1w`.
     Please see [`MP2RAGE` specific notes](/99-appendices/11-qmri.html#unit1-images)
     in the qMRI appendix for further information.
 VFA: