diff --git a/2019/mills/Makefile b/2019/mills/Makefile
index 5b782f335..e2cbecdb3 100644
--- a/2019/mills/Makefile
+++ b/2019/mills/Makefile
@@ -288,7 +288,8 @@ all: data ${TARGET}
 .PHONY: all alt data everything diff_orig_prog diff_prog_orig \
 	diff_alt_prog diff_prog_alt diff_orig_alt diff_alt_orig \
 	clean clobber install love haste waste maker easter_egg \
-	sandwich supernova deep_magic magic charon pluto
+	sandwich supernova deep_magic magic charon pluto \
+	text
 
 ${TARGET}: ${PROG}.c Makefile ${INPUTS}
 	${CC} ${CFLAGS} -o $@ $< $($@) ${LDFLAGS}
@@ -306,6 +307,9 @@ data: ${DATA}
 ${INPUTS}: %.txt: %.txt.gz
 	${ZCAT} < $< > $@
 
+text: ${INPUTS}
+	@${TRUE}
+
 test: ${OUTPUTS}
 
 # First 1000 lines of generated output
diff --git a/2019/mills/README.md b/2019/mills/README.md
index bc04b3f53..5216e36ea 100644
--- a/2019/mills/README.md
+++ b/2019/mills/README.md
@@ -245,11 +245,21 @@ validation loss is about 1.72.  Comparing the validation loss and the
 training loss will give you an idea of how well the network is learning and
 can let you know if the network is [overfitting or underfitting][7].
 
-As part of the training process, the data set (which for OMLET is the
-[Shakespeare.txt](Shakespeare.txt)file you gave on the command line) is divided into
+As part of the training process, the data set, which for OMLET is a
+file you gave on the command line, is divided into
 [training and validation sets][8] (by default, 95% of the data is used for
 training, but like most OMLET parameters, you can change this at compile-time).
 
+For examples of input text files, try:
+
+``` <!---sh-->
+    make text
+```
+
+and then examine the resulting `IOCCC-hints.output.txt`
+`Shakespeare.output.txt` `IOCCC-Rules-Guidelines.output.txt`
+`Eugene_Onegin.output.txt` temporary files.
+
 At the end of the validation run, OMLET writes out a checkpoint file with a
 name like `cp01_1.970`.  This saves the state of the run at the start of the
 epoch 1, after computing a validation loss of 1.970.  The checkpoint is
diff --git a/2019/mills/index.html b/2019/mills/index.html
index b85704ce1..13d6f8bbf 100644
--- a/2019/mills/index.html
+++ b/2019/mills/index.html
@@ -577,10 +577,15 @@ looks like</p>
 validation loss is about 1.72. Comparing the validation loss and the
 training loss will give you an idea of how well the network is learning and
 can let you know if the network is <a href="https://en.wikipedia.org/wiki/Overfitting">overfitting or underfitting</a>.</p>
-<p>As part of the training process, the data set (which for OMLET is the
-<a href="Shakespeare.txt">Shakespeare.txt</a>file you gave on the command line) is divided into
+<p>As part of the training process, the data set, which for OMLET is a
+file you gave on the command line, is divided into
 <a href="https://en.wikipedia.org/wiki/Training,_validation,_and_test_sets">training and validation sets</a> (by default, 95% of the data is used for
 training, but like most OMLET parameters, you can change this at compile-time).</p>
+<p>For examples of input text files, try:</p>
+<pre><code>    make text</code></pre>
+<p>and then examine the resulting <code>IOCCC-hints.output.txt</code>
+<code>Shakespeare.output.txt</code> <code>IOCCC-Rules-Guidelines.output.txt</code>
+<code>Eugene_Onegin.output.txt</code> temporary files.</p>
 <p>At the end of the validation run, OMLET writes out a checkpoint file with a
 name like <code>cp01_1.970</code>. This saves the state of the run at the start of the
 epoch 1, after computing a validation loss of 1.970. The checkpoint is