From 3ef56d2c52efe5c5b43ea26ebe8d4c7a9d4df482 Mon Sep 17 00:00:00 2001 From: deeaitch Date: Sat, 28 Feb 2026 22:20:44 -0500 Subject: [PATCH] update readme. --- README.md | 12 ++---------- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 561656d..114ed28 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ The tool parses Kindle highlights and groups them by book title, producing a LaT * `\section{}` — per book * `\subsection{}` — per highlight (metadata line) * Highlight text — inserted as plain LaTeX content -* ` \subsubsection{notes}` — placeholder for future comments +* `\subsubsection{notes};` — placeholder for future comments --- @@ -83,7 +83,7 @@ Generated LaTeX structure: \subsection{- Your Highlight on Location 123-125 | Added on ...} Highlighted text line 1 Highlighted text line 2 - \subsubsection{notes}; + \subsubsection{notes} ``` Highlights are grouped by book title. @@ -133,11 +133,3 @@ This repository intentionally keeps two different parsing styles: * The TypeFactory version demonstrates a clean, extensible runtime pipeline. The goal is architectural exploration and comparison, not just solving the parsing task. - ---- - -If you want, I can also add: - -* A small diagram of the parsing stages -* A section comparing performance characteristics -* Or a short "When to choose FSM vs Factory" guideline for future reuse in your blueprints repository