From 9fb68da889595e73ae1692be951fe3816d473fc1 Mon Sep 17 00:00:00 2001
From: Timotej Lazar <timotej.lazar@fri.uni-lj.si>
Date: Tue, 6 Feb 2018 15:18:34 +0100
Subject: Tweak more

---
 aied2018/patterns.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'aied2018/patterns.tex')

diff --git a/aied2018/patterns.tex b/aied2018/patterns.tex
index d50a62e..28a5ed8 100644
--- a/aied2018/patterns.tex
+++ b/aied2018/patterns.tex
@@ -127,7 +127,7 @@ The first TRE encodes a single path in the AST and describes the program’s blo
             print(d)
 \end{Verbatim}
 
-The second pattern describes a common mistake for this problem: \code{range(1,n)} will only generate values up to \code{n-1}, so \code{n} will not be printed as its own divisor. A correct pattern would include the binary operator \code{+} on the path to \code{n}, indicating a call to \code{range(1,n+1)}.
+The second pattern shows a common mistake for this problem: \code{range(1,n)} will only generate values up to \code{n-1}, so \code{n} will not be printed as its own divisor. A correct pattern would include the binary operator \code{+} on the path to \code{n}, indicating a call to \code{range(1,n+1)}.
 
 \subsection{Constructing patterns}
 
-- 
cgit v1.2.1

