From 89df888f2c8560dd34b51ad89cfa2ce1c3d3d685 Mon Sep 17 00:00:00 2001
From: Alice BRENON <alice.brenon@ens-lyon.fr>
Date: Wed, 27 Nov 2024 13:17:00 +0100
Subject: [PATCH] Fix typos
---
ICHLL_Brenon.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/ICHLL_Brenon.md b/ICHLL_Brenon.md
index fbab2a2..b406490 100644
--- a/ICHLL_Brenon.md
+++ b/ICHLL_Brenon.md
@@ -241,7 +241,7 @@ subgenre departing from them in terms of purpose.
# The *dictionaries* TEI module {#sec:dictionaries-module}
-One of the main motivation behind project DISCO-LGE was to produce data useful
+One of the main motivations behind project DISCO-LGE was to produce data useful
to future scientific projects, which in particular requires it to be
*interoperable* and *reusable*. These are the two last key aspects of the FAIR
([https://www.go-fair.org/fair-principles/](https://www.go-fair.org/fair-principles/))
@@ -478,7 +478,7 @@ apparatus — is less clear, is to wrap together several versions of the same
excerpts, for instance when there are several possible readings of an unclear
group of words in a manuscript, or when the encoder is trying to compile a
single version of a piece of work from several sources which disagree over some
-passage. In both case, it appears obvious that it is not something that is
+passage. In both cases, it appears obvious that it is not something that is
expected to occur naturally in the course of an article in general.
Thus, despite a rather dense internal connectivity, the *dictionaries* module
@@ -673,7 +673,7 @@ not mere remarks in the margins or at the foot of pages.
The remarks made in section @sec:dictionaries-module explain why the
*dictionary* module is unable to represent encyclopedias, where the notion of
-"meaning" is less central that in dictionaries and where discourse with nested
+"meaning" is less central than in dictionaries and where discourse with nested
structures of arbitrary depth can occur. Even composite encodings using elements
outside of the *dictionaries* module under an `<entry/>` element do not meet the
requirements of the project. Since the *core* module obviously accomodates these
--
GitLab