[FIX] Minor fixups of inconsistencies while going through a PDF version

src/04-modality-specific-files/02-magnetoencephalography.md

@@ -90,7 +90,7 @@ Specific MEG fields MUST be present:
 | DigitizedLandmarks  | REQUIRED. Boolean ("true" or "false") value indicating whether anatomical landmark points (i.e. fiducials) are contained within this recording.                                                                                                                                                                                                                                                                                   |
 | DigitizedHeadPoints | REQUIRED. Boolean (`true` or `false`) value indicating whether head points outlining the scalp/face surface are contained within this recording.                                                                                                                                                                                                                                                                                  |
 
-SHOULD be present
+SHOULD be present:
 
 | Field name                 | Definition                                                                                                                                                                                                                                                                                                                                                                                          |
 | :------------------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -162,7 +162,7 @@ Example:
 ```
 
 Note that the date and time information SHOULD be stored in the Study key file
-(`scans.tsv`), see [Scans.tsv](../03-modality-agnostic-files.md#scans-file). As
+(`scans.tsv`), see [Scans file](../03-modality-agnostic-files.md#scans-file). As
 it is indicated there, date time information MUST be expressed in the following
 format `YYYY-MM-DDThh:mm:ss`
 ([ISO8601](https://en.wikipedia.org/wiki/ISO_8601) date-time format). For

src/04-modality-specific-files/05-task-events.md

@@ -11,7 +11,7 @@ sub-<label>/[ses-<label>]
 
 Where `<matches>` corresponds to task file name. For example:
 `sub-control01_task-nback`. It is also possible to have a single \_events.tsv
-file describing events for all participants and runs (see ["Inheritance rule"](../02-common-principles.md#the-inheritance-principle)).
+file describing events for all participants and runs (see [Inheritance Principle](../02-common-principles.md#the-inheritance-principle)).
 As with all other tabular data, `_events` files may be
 accompanied by a JSON file describing the columns in detail (see [here](../02-common-principles.md#tabular-files)).
 
@@ -24,7 +24,7 @@ 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). Each task events file REQUIRES a corresponding task imaging data file
 (but a single events file MAY be shared by multiple imaging data files - see
-Inheritance rule). The tabular files consists of one row per event and a set of
+Inheritance principle). The tabular files consists of one row per event and a set of
 REQUIRED and OPTIONAL columns:
 
 | Column name   | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |

src/99-appendices/03-hed.md

@@ -75,5 +75,5 @@ The tags in the `HED` column are often specific to the event instances, while
 the common properties associated with categories such as `mycodes` are
 encapsulated in the \_events.json dictionary. Downstream tools should not
 distinguish between tags specified using the different mechanisms. Further,
-the normal BIDS inheritance rules apply so these data dictionaries can appear
-higher in the BIDS hierarchy.
+the normal BIDS inheritance principle applies so these data dictionaries can
+appear higher in the BIDS hierarchy.