From 62131075aef5cd3cff6b8814511753079c3f3325 Mon Sep 17 00:00:00 2001
From: Eric Zhao <21zhaoe@protonmail.com>
Date: Tue, 10 Oct 2023 02:49:51 -0400
Subject: [PATCH] formalism: Clean up preface

---
 formalism/preface.tex | 13 +++++--------
 1 file changed, 5 insertions(+), 8 deletions(-)

diff --git a/formalism/preface.tex b/formalism/preface.tex
index 5e17e04..a7e9ddb 100644
--- a/formalism/preface.tex
+++ b/formalism/preface.tex
@@ -3,7 +3,7 @@
 \begin{document}
 \section{Preface}
 \label{sec:preface}
-This is a formalism demonstrating the \emph{marked lambda calculus}, a judgmental framework for
+This is the complete formalism demonstrating the \emph{marked lambda calculus}, a judgmental framework for
 precise bidirectional error localization and recovery that employs gradual typing.
 
 \subsection{Organization}
@@ -18,20 +18,17 @@ \subsection{Organization}
     polymorphism.
 
   \item \cref{sec:untyped} gives a version of the Hazelnut structure editor calculus that uses the
-    marked lambda calculus to solve Hazelnut's deficiency with regards to non-local hole fixing.
+    marked lambda calculus to solve Hazelnut's deficiency with regards to non-local hole fixes.
 
   \item \cref{sec:typed} is similar, except that it employs the marking procedure in a roughly
     incremental fashion.
 \end{itemize}
 %
-Note that each of the following sections after \cref{sec:marked} build upon the same core language.
+Note that each of the sections following \cref{sec:marked} build upon that same core language.
 
 \subsection{Mechanization}
-Not all parts of the formalism are mechanized in Agda. In particular, the core of the marked lambda
-calculus (\cref{sec:marked}) and the untyped Hazelnut calculus that employs marking
-(\cref{sec:untyped}) \emph{are} mechanized, while all others \emph{are not}. Crucially, the
-metatheorems of the aforementioned sections are verified, whereas those of all other sections are
-not.
+Not all parts of the formalism are mechanized in Agda. It is noted in each section whether or not
+the section has been mechanized and, if so, where to find the relevant definitions and theorems.
 
 As possible, the names of judgments and rules that appear in the mechanization have been made to
 follow those in this formalism. Refer also to the mechanization's README for more details.