From fe907be6d31ae21a3da722edddf49aeedd02d71a Mon Sep 17 00:00:00 2001
From: Jonas Smedegaard <dr@jones.dk>
Date: Sat, 24 May 2025 13:43:16 +0200
Subject: misc grammar and avoidance of abbreviations

---
 _intro.qmd | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

(limited to '_intro.qmd')

diff --git a/_intro.qmd b/_intro.qmd
index ad0d5e4..f63f79c 100644
--- a/_intro.qmd
+++ b/_intro.qmd
@@ -16,12 +16,12 @@ But Markdown can only express structure and hypermedia annotations,
 not semantic annotations.  
 Annotating text differs from annotating the document as a whole
 in that the information is tied to specific text strings.
-A document annotation can say
-e.g. "this document contains strong language somewhere"
-or "this document contains a link to this URL somwehere",
-whereas a text annotation can say
-e.g. "this text string is strongly emphasized"
-or "this text string links to this URL".
+A document annotation can state, for example,
+"this document contains strong language somewhere"
+or "this document contains a link to this URL somewhere",
+whereas a text annotation can state, for example,
+"this text string is strongly emphasized"
+or "this text string links to this URL."
 
 Semantic text annotation
 is the process of applying information about meaning
@@ -49,7 +49,7 @@ by way of a Pandoc filter to handle semantic text annotations.
 
 ## Problem formulation
 
-So,
+Thus,
 **how can Pandoc be extended to support semantic text annotations?**
 
 * What are the core qualities of Markdown,
@@ -114,7 +114,7 @@ however,the latter, if successful, is likely to be far more reliable.
 
 This project aims at introducing new syntax
 while staying close to existing Markdown,
-unlike e.g. SAM that deviates notably from Markdown
+unlike, for example, SAM that deviates notably from Markdown
 [@SAM2018].
 
 Many Markdown processors exist,
-- 
cgit v1.2.3

