From a6c05e160cb61d959fae7b7dcbea19e332e6684f Mon Sep 17 00:00:00 2001 From: Dylan Stephano-Shachter Date: Thu, 30 May 2024 22:05:26 +0300 Subject: [PATCH] Typo in README.md (#472) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2d359b9d..45e8eaa9 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,7 @@ If you are looking for FamilySearch's GEDCOM 5.5.1 Java parser, which previously - [`changelog.md`](changelog.md) is a running log of major changes made to the specification. - [`exid-types.json`](exid-types.json) is a JSON file containing registered EXID-TYPE values. - [`specification/`](specification/) contains the FamilySearch GEDCOM specification: - - `specification/gedcom-`number`-`title`.md` files are the source documents used to define the FamilySearch GEDCOM specification. It is written in pandoc-flavor markdown and is intended to be more easily written than read. It is splint into several files (ordered by the integer in their names) to facilitate comparing files. + - `specification/gedcom-`number`-`title`.md` files are the source documents used to define the FamilySearch GEDCOM specification. It is written in pandoc-flavor markdown and is intended to be more easily written than read. It is split into several files (ordered by the integer in their names) to facilitate comparing files. - In a local check-out, this is also where the build scripts place rendered files `gedcom.html` and `gedcom.pdf`; see [releases](releases/latest) for a pre-rendered copy of these. - [`specification/terms/`](specification/terms/) - YAML files to be served in the namespace, augmenting those automatically extracted from the specification itself by [`build/uri-def.py`](build/uri-def.py).