about summary refs log tree commit diff
diff options
context:
space:
mode:
authorArun Isaac2025-09-01 13:38:44 +0100
committerArun Isaac2025-09-01 15:04:30 +0100
commit1d1b31154f04af9f262fa1a0baf357aa4753bb59 (patch)
tree9c11957bad6409fe051cea435aeb53e8f43594f0
parent48cd79a75f274a2bdffbefc508e2a0e4be96f34d (diff)
downloadpyhegp-1d1b31154f04af9f262fa1a0baf357aa4753bb59.tar.gz
pyhegp-1d1b31154f04af9f262fa1a0baf357aa4753bb59.tar.lz
pyhegp-1d1b31154f04af9f262fa1a0baf357aa4753bb59.zip
Title case sentence.
-rw-r--r--doc/file-formats.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/file-formats.md b/doc/file-formats.md
index 8515b38..01263e3 100644
--- a/doc/file-formats.md
+++ b/doc/file-formats.md
@@ -30,7 +30,7 @@ chr11	3464016	A	-0.2400	0.1623
 
 The genotype file is a tab-separated values (TSV) file. The first line MUST be a header with column labels. Each row corresponds to one SNP. The columns labelled `chromosome`, `position` and `reference` contain the chromosome, the position on the chromosome and the reference allele for that SNP. Other columns each contain dosage values for one sample. The headers of these columns MUST be their sample identifiers. Column headers are case-sensitive.
 
-the `reference` column is optional, and should be absent in encrypted genotype files.
+The `reference` column is optional, and should be absent in encrypted genotype files.
 
 Here is an example genotype file.
 ```