add more links

includes/abbreviations.md

@@ -5,12 +5,24 @@
 *[BEPs]: BIDS Extension Proposals
 *[BIDS]: Brain Imaging Data Structure
 *[DOI]: Digital Object Identifiers
+*[EEG]: Electroencephalography
+*[iEEG]: Intracranial Electroencephalography
 *[JSON]: JavaScript Object Notation
+*[MEG]: Magnetoencephalography
 *[MRI]: Magnetic Resonance Imaging
 *[NIRS]: Near-InfraRed Spectroscopy
 *[PET]: Positron Imaging Tomography
 *[TSV]: Tab Separated Values
 *[URI]: Uniform Resource Identifier
 *[URL]: Uniform Resource Locator
-*[subject]: A person or animal participating in the study. Used interchangeably with term **Participant**.
-*[task]: A set of structured activities performed by the participant (see [glossary](https://bids-specification.readthedocs.io/en/latest/glossary.html#task-common_principles))
+
+*[dataset]: A set of neuroimaging and behavioral data acquired for a purpose of a particular study. A dataset consists of data acquired from one or more subjects, possibly from multiple sessions.
+*[derivatives]: Derivatives are outputs of common processing pipelines, capturing data and meta-data sufficient for a researcher to understand and (critically) reuse those outputs in subsequent processing.
+*[entity]: An "entity" is an attribute that can be associated with a file, contributing to the identification of that file as a component of its filename in the form of a hyphen-separated key-value pair.
+*[event] Something that happens or may be perceived by a test subject as happening at a particular instant during the recording.
+*[run]: An uninterrupted repetition of data acquisition that has the same acquisition parameters and task (however events can change from run to run due to different subject response or randomized nature of the stimuli). Run is a synonym of a data acquisition.
+*[sample]: A sample pertaining to a subject such as tissue, primary cell or cell-free sample.
+*[session]: A logical grouping of neuroimaging and behavioral data consistent across subjects. Session can (but doesn't have to) be synonymous to a visit in a longitudinal study.
+*[subject]: A person or animal participating in the study. Used interchangeably with term Participant.
+*[suffix]: An alphanumeric string that forms part of a filename, located after all entities and following a final `_`, right before the file extension.
+*[task]: A set of structured activities performed by the participant.

src/appendices/qmri.md

@@ -219,7 +219,7 @@ in the [BIDS examples](https://bids-standard.github.io/bids-examples/#qmri).
 
 The table of required entities for qMRI file collections are provided in the [entity table](./entity-table.md).
 However, viability of a qMRI file collection is determined not only by the naming and organization of the input files,
-but also by which metadata fields are provided in accompanying json files.
+but also by which metadata fields are provided in accompanyingJSONfiles.
 
 ### Method-specific priority levels for qMRI file collections
 
@@ -380,10 +380,10 @@ a proper interpretation of qMRI maps may critically depend on some metadata fiel
 For example, without the information of `MagneticFieldStrength`, white-matter T1 values in a `T1map` become elusive.
 
 -   All the acquisition parameters that are constant across the files in a file collection are RECOMMENDED
-    to be added to the sidecar json of the qMRI maps.
+    to be added to the sidecarJSONof the qMRI maps.
 
 -   Relevant acquisition parameters that vary across files in a qMRI file collection are RECOMMENDED
-    to be added to the sidecar json of the qMRI map **in array form**.
+    to be added to the sidecarJSONof the qMRI map **in array form**.
 
 -   The JSON file accompanying a qMRI map which is obtained by using open-source software is RECOMMENDED
     to include additional metadata fields listed in the following table:

src/appendices/schema.md

@@ -10,7 +10,7 @@ to the BIDS standard.
 The BIDS schema is available in two machine readable formats:
 
 -   as a set of [YAML](https://en.wikipedia.org/wiki/YAML) files in the [BIDS specification repository](https://github.com/bids-standard/bids-specification/tree/master/src/schema)
--   as a [single dereferenced json file](https://bids-specification.readthedocs.io/en/stable/schema.json)
+-   as a [single dereferencedJSONfile](https://bids-specification.readthedocs.io/en/stable/schema.json)
 
 A didactic walkthrough of the schema can be found in the [BEP Guide](https://bids-extensions.readthedocs.io/en/latest/schema/),
 and a complete description is available in the [`bidsschematools` documentation](https://bidsschematools.readthedocs.io/en/latest/).