git » jacl.git » commit 6b3e657

diff --git a/paper/jacl-els-2020.tex b/paper/jacl-els-2020.tex
index 8e01155..07d7b85 100644
--- a/paper/jacl-els-2020.tex
+++ b/paper/jacl-els-2020.tex
@@ -509,9 +509,9 @@ JavaScript sequence and so is used as placeholder syntax.
 
 \subsection{Delivery}
 
-All of the JACL features I have described so far are in the very early
-stages of implementation, but JACL's delivery capabilities have yet to
-be implemented at all.
+All of the JACL features described so far are in the very early stages
+of implementation, but JACL's delivery capabilities have yet to be
+implemented at all.
 
 Fortunately, since JACL development is image-based, JACL should
 support the traditional approach of specifying a Lisp function
@@ -547,12 +547,9 @@ to code generation will ultimately be best.
 
 \section{Conclusions and Future Work}
 
-I have presented a new Common Lisp, JACL, which was created to ease
-SPA development by applying the power of Common Lisp and interactive
-development to contemporary Web development challenges.
-
-I have described four novel aspects of JACL with respect to other
-comparable, contemporary Lisp implementations:
+JACL, a new Common Lisp created to ease SPA development, was
+introduced. Four novel aspects of JACL were described with respect to
+other, comparable Lisp implementations:
 
 \begin{enumerate}
   \item Asynchronous reader.
@@ -561,19 +558,18 @@ comparable, contemporary Lisp implementations:
   \item Delivery facility design.
 \end{enumerate}
 
-While most of Common Lisp that JACL will be capable of supporting
-remains to be implemented, JACL is nearly in a state in which it can
-be used for application development.
+Most of Common Lisp that JACL will be capable of supporting remains
+unimplemented. However, JACL is nearly in a state in which it can be
+used for application development.
 
 The most immediate body of remaining work is population of the
 \texttt{COMMON-LISP} package, towards the end goal of supporting MIT
-\texttt{LOOP}. Such support would imply comprehensive support of many
+\texttt{LOOP}. Such support would imply comprehensive support for many
 fundamental Lisp operators.
 
-A longer term but equally important goal is CLOS support. Key
-historical Lisp innovations were achieved with CLOS or one of its
-predecessors, and so its ultimate inclusion is an important project
-goal.
+A longer term goal is support for the Common Lisp Object System
+(CLOS). Key historical Lisp innovations were achieved with CLOS or one
+of its predecessors, and so its inclusion is a high priority.
 
 Many other design and implementation tasks remain, such as support for
 special variables in lambda lists, \texttt{EVAL-WHEN}, macro lambda
@@ -584,7 +580,7 @@ application development.
 
 Bootstrapping is a desirable milestone, but since the fact that JACL
 is not currently bootstrapped doesn't preclude its use for application
-development, this work is low priority.
+development, bootstrapping is not a high priority.
 
 \section{Acknowledgments}