aboutsummaryrefslogtreecommitdiff
path: root/gnu/packages/tex.scm
diff options
context:
space:
mode:
Diffstat (limited to 'gnu/packages/tex.scm')
-rw-r--r--gnu/packages/tex.scm8
1 files changed, 4 insertions, 4 deletions
diff --git a/gnu/packages/tex.scm b/gnu/packages/tex.scm
index 31c2c4cfd1..324b8eeeee 100644
--- a/gnu/packages/tex.scm
+++ b/gnu/packages/tex.scm
@@ -193,7 +193,7 @@
;;;
;;; Thanks to the `texlive' updater, the more tedious part of that task, i.e.,
;;; refreshing version strings, hashes, possibly locations and inputs, is
-;;; automated. Yet, the following additional steps are required; they can
+;;; automated. Yet, the following additional steps are required, and they can
;;; keep one busy for a while:
;;;
;;; 1. First and foremost, run the updater:
@@ -220,10 +220,10 @@
;;; 4. Handle inputs issues. No updater is allowed to create an input field
;;; in a package if it didn't exist beforehand. `texlive' updater is no
;;; exception; it cannot update, e.g., propagated inputs if the relative
-;;; package don't propagate inputs already. Double check updater's output,
-;;; such issues are mentioned, and resolve them manually.
+;;; package didn't propagate some inputs already. Double check updater's
+;;; output, such issues are mentioned, and resolve them manually.
;;;
-;;; Likewise, look for (list) artefacts the updater may have scattered
+;;; Likewise, look for `(list)' artefacts the updater may have scattered
;;; throughout this module. They usually appear when all elements have
;;; been removed from an input field. In this situation, for aesthetics,
;;; the whole field can be suppressed.