[latex3-commits] [latex3/tagging-project] main: typos (798b21d)

[github at latex-project.org]

Repository : https://github.com/latex3/tagging-project
On branch  : main
Link       : https://github.com/latex3/tagging-project/commit/798b21deb3e56da9efdf6283cca29085a06ba468

>---------------------------------------------------------------

commit 798b21deb3e56da9efdf6283cca29085a06ba468
Author: Ulrike Fischer <fischer at troubleshooting-tex.de>
Date:   Thu Jul 13 00:16:44 2023 +0200

    typos


>---------------------------------------------------------------

798b21deb3e56da9efdf6283cca29085a06ba468
 README.md | 13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 0a973c8..d562122 100644
--- a/README.md
+++ b/README.md
@@ -6,9 +6,16 @@ Issues related to the tagging project
 
 This repository does not contain any code.
 
-It is meant to track issues and suggestions related to "LaTeX Tagged PDF" project. The code for this project is split over several other repositories (latex2e, latex3, taggpdf,... to name a few) and so this here is a convenient place to to keep any more general topics or issues that cut across the different repositories in a single place.
-
-If an issue recorded here requires changes in the other repositories sub-issues can then be opend (by us) in those repositories and linked back, or, if such changes are confined to a single repository, the issue could be transfered there -- whatever is more appropriate.
+It is meant to track issues and suggestions related to the "LaTeX Tagged PDF" 
+project. The code for this project is split over several other repositories 
+(latex2e, latex3, tagpdf,... to name a few) and so this here is a convenient 
+place to  keep any more general topics or issues that cut across the 
+different repositories in a single place. 
+
+If an issue recorded here requires changes in the other repositories 
+sub-issues can then be opened (by us) in those repositories and linked back, 
+or, if such changes are confined to a single repository, the issue could be 
+transferred there -- whatever is more appropriate. 
 
 
 ## License