tidying

Author: tompollard

_config.yml

@@ -11,7 +11,7 @@ callouts:
     title: Note
     color: red
   important:
-    title: Note
+    title: 
     color: blue
   citation:
     title: Citation

index.md

@@ -8,7 +8,8 @@ nav_order: 1
 
 Welcome to the website for the **Waveform Database (WFDB)** project.
 
-WFDB defines a set of open standards and software tools for the storage, sharing, and analysis of physiologic signal and annotation data. It has been widely used for decades to support biomedical research, clinical studies, and education.
+{: .important }
+> WFDB defines a set of open standards and software tools for the storage, sharing, and analysis of physiologic signal and annotation data. It has been widely used for decades to support biomedical research, clinical studies, and education.
 
 ---
 

spec/annotation-files.md

@@ -7,8 +7,7 @@ nav_order: 4
 
 # WFDB Annotation Files
 
-Annotation files contain **time-stamped event markers** aligned to the signal data.  
-These files provide critical context, such as heartbeat labels, arrhythmias, rhythm changes, and comments.
+Annotation files contain **time-stamped event markers** aligned to the signal data.  These files provide critical context, such as heartbeat labels, arrhythmias, rhythm changes, and comments.
 
 WFDB supports two annotation file formats:
 
@@ -19,16 +18,14 @@ WFDB supports two annotation file formats:
 
 ## MIT Annotation Format
 
-The MIT format is the **standard** for WFDB annotations.  
-It is binary, compact (averaging slightly over two bytes per annotation), and extensible.
+The MIT format is the **standard** for WFDB annotations.  It is binary, compact (averaging slightly over two bytes per annotation), and extensible.
 
 Each annotation in the MIT format consists of:
 
 - A **time difference** (`I`) from the previous annotation, measured in sample intervals.
 - An **annotation type code** (`A`), describing the event.
 
-The first byte of each annotation pair is the **least significant byte**.  
-The six most significant bits across the pair encode the annotation type, and the remaining ten bits encode the time difference.
+The first byte of each annotation pair is the **least significant byte**.  The six most significant bits across the pair encode the annotation type, and the remaining ten bits encode the time difference.
 
 ---
 

spec/file-structure.md

@@ -7,7 +7,8 @@ nav_order: 1
 
 # Overview of the WFDB File Structure
 
-A WFDB (Waveform Database) record typically consists of **multiple related files** that together define a physiologic signal recording and its annotations.
+{: .important }
+> A WFDB (Waveform Database) record typically consists of **multiple related files** that together define a physiologic signal recording and its annotations.
 
 The key file types are:
 
@@ -40,6 +41,7 @@ For example, for a record named `100`, the typical files might be:
 ## Multi-Segment Records
 
 Some WFDB records are **multi-segment**. In this case, the main header file references a sequence of segments, each with its own associated files.  
+
 Multi-segment records allow for efficient storage of long recordings and variable signal structures.
 
 ---

spec/header-files.md

@@ -7,7 +7,7 @@ nav_order: 2
 
 # WFDB Header Files
 
-Each WFDB record includes one or more **header file** (`.hea`) that specify the associated signal files and their attributes. Header files are plain ASCII text and are critical for interpreting the associated signal and annotation files.
+Each WFDB record includes one or more **header files** (`.hea`) that specify the associated signal files and their attributes. Header files are plain ASCII text and are critical for interpreting the associated signal and annotation files.
 
 ---
 

spec/signal-files.md

@@ -7,8 +7,7 @@ nav_order: 3
 
 # WFDB Signal Data Files
 
-WFDB signal files contain the raw waveform data for one or more signals.  
-Each file is typically in a binary format optimized for efficient storage and processing.
+WFDB signal files contain the raw waveform data for one or more signals.  Each file is typically in a binary format optimized for efficient storage and processing.
 
 Signal files are referenced in the corresponding **header file** (`.hea`), which specifies the format used for each signal.