Address review comments: improve events documentation clarity

- Remove 'task' from 'task events section' references
- Reword events.md introduction to be more inclusive of non-task events
- Fix grammar: 'Please mind' to 'Please keep in mind'
- Clarify that 'Each events.tsv file' (not just 'events file')
- Update historical references in changelogs

Author: neuromechanist

src/common-principles.md

@@ -677,7 +677,7 @@ Example of a hypothetical `*_bold.json` file, accompanying a `*_bold.nii` file:
 Example of a hypothetical `*_events.json` file, accompanying an
 `*_events.tsv` file. Note that the JSON file contains a key describing an
 *arbitrary* column `stim_presentation_side` in the TSV file it accompanies.
-See [task events section](modality-agnostic-files/events.md)
+See [events section](modality-agnostic-files/events.md)
 for more information.
 
 ```JSON

src/modality-agnostic-files/events.md

@@ -2,12 +2,13 @@
 
 The purpose of this file is to describe timing and other properties of events
 recorded during data acquisition.
-Events are, for example, stimuli presented to the participant or participant responses
-during acquisition of functional data and thus associated with specific tasks performed
-(see [Definitions](../common-principles.md#definitions)).
+Events may include stimuli presented to the participant, participant responses
+that are associated with tasks, or markers of other incidents that occurred
+during the execution of the experiment.
+See the [definition of Event](../common-principles.md#definitions) for a more detailed explanation.
 A single event file MAY include any combination of stimulus, response, and other events.
 Events MAY overlap in time.
-Please mind that this does not imply that only so called "event related" study designs
+Please keep in mind that this does not imply that only so called "event related" study designs
 are supported (in contrast to "block" designs) - each "block of events" can be
 represented by an individual row in the `events.tsv` file (with a long
 duration).
@@ -19,7 +20,7 @@ duration).
    )
 }}
 
-Each events file REQUIRES a corresponding data file.
+Each `events.tsv` file REQUIRES a corresponding data file.
 It is also possible to have a single `events.tsv` file describing events
 for all participants and runs (see
 [Inheritance Principle](../common-principles.md#the-inheritance-principle)).

src/pregh-changes.md

@@ -9,7 +9,7 @@
 
 -   Added support for MEG data (merged BEP008).
 -   Added `SequenceName` field.
--   Added support for describing events with Hierarchical Event Descriptors: [4.3 Task events](modality-agnostic-files/events.md).
+-   Added support for describing events with Hierarchical Event Descriptors: [4.3 Events](modality-agnostic-files/events.md).
 -   Added `VolumeTiming` and `AcquisitionDuration` fields: [4.1 Task (including resting state) imaging data](modality-specific-files/magnetic-resonance-imaging-data.md#task-including-resting-state-imaging-data).
 -   Added `DwellTime` field.