From 92b761c2df18d8f1c27a0d44c68b2e807790e578 Mon Sep 17 00:00:00 2001
From: Alice BRENON <alice.brenon@ens-lyon.fr>
Date: Tue, 3 Sep 2024 08:58:00 +0200
Subject: [PATCH] More typos

---
 ICHLL_Brenon.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ICHLL_Brenon.md b/ICHLL_Brenon.md
index 9628489..6626fb8 100644
--- a/ICHLL_Brenon.md
+++ b/ICHLL_Brenon.md
@@ -85,7 +85,7 @@ features of a source document, the transcription of oral corpora or particular
 requirements for textual domains like poetry, or, in the case at hand,
 dictionaries. The intrinsic complexity of dictionaries has been well identified
 since the inception of the project [@tei_vault] and @ide_encoding_1995
-underlines the amount of work which went into the third version of the
+underline the amount of work which went into the third version of the
 guidelines (P3) to provide a toolbox both general and expressive enough to
 account for the variety of conventions found in dictionaries. This module has
 been successfully used to encode both historical [@williams2017; @bohbot2018]
@@ -661,7 +661,7 @@ human editing the text from a given physical copy of it), but it is
 unfortunately of no use to encode a section of an article.
 
 The first element that might at least seem acceptable is the last one,
-`<note/>`. It is meant to contain text, is about explaning something and seems
+`<note/>`. It is meant to contain text, is about explaining something and seems
 general enough (not specific to a given genre, or to the occurrence of a
 particular object on the page). Unfortunately, its semantics still seems a bit
 off compared to what is required. The documentation describes it as an
-- 
GitLab