tex: stylistical stuff

tex/text.tex

@@ -1400,8 +1400,8 @@ the table schema and relations entirely in Go.
 The best part about ent is that there is no need to define supplemental methods
 on the models, since with ent these are meant to be \emph{code generated} (in
 the older sense of word, not with Large Language Models). That creates files
-with models based on the types of the attributes in the database model and the
-respective relations are transformed into methods on the receiver and functions
+with models based on the types of the attributes in the database model, and the
+respective relations are transformed into methods on the receiver or functions
 taking object attributes as arguments.
 
 For instance, if the model's attribute is a string value \texttt{Email}, ent
@@ -1415,14 +1415,14 @@ following:
 \item \texttt{EmailHasSuffix(suffix string)}
 \end{itemize}
 
-These methods can further be imported into other packages and makes working
-with the database a morning breeze.
+These methods can further be imported into other packages and this makes
+working with the database a morning breeze.
 
 
 \n{1}{Production}
 
-It is, of course, recommended that the application runs in a secure
-environment although definitions of that almost certainly differ depending on
+It is, of course, recommended that the application runs in a secure environment
+\allowbreak although definitions of that almost certainly differ depending on
 who you ask. General recommendations would be either to effectively reserve a
 machine for a single use case - running this program - so as to dramatically
 decrease the potential attack surface of the host, or run the program isolated