summaryrefslogtreecommitdiff
path: root/prolog/problems/lists/conc_3
diff options
context:
space:
mode:
authorAleksander Sadikov <aleksander.sadikov@fri.uni-lj.si>2016-08-28 23:07:01 +0200
committerAleksander Sadikov <aleksander.sadikov@fri.uni-lj.si>2016-08-28 23:07:01 +0200
commit918513a870273ab70e6ea60ab25344b77a44fec3 (patch)
tree4beb23128ed1e28dacc5dbebcd2ec51f1f786e17 /prolog/problems/lists/conc_3
parentca743bffb497dea794950bf2bbda45e3bb4c936b (diff)
English translation for memb/2 added.
Diffstat (limited to 'prolog/problems/lists/conc_3')
-rw-r--r--prolog/problems/lists/conc_3/en.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/prolog/problems/lists/conc_3/en.py b/prolog/problems/lists/conc_3/en.py
index 2e74e5e..c384222 100644
--- a/prolog/problems/lists/conc_3/en.py
+++ b/prolog/problems/lists/conc_3/en.py
@@ -30,7 +30,7 @@ hint = {
'eq_instead_of_equ': '''\
<p>The operator <code>==</code> is "stricter" than operator <code>=</code> in the sense that
for the latter it is enough to be able to make the two operands equal (unification). Perhaps by using <code>=</code>
-you can make the predicate <code>rev/2</code> more general (e.g. able to work with output arguments becoming inputs).</p>
+you can make the predicate <code>conc/3</code> more general (e.g. able to work with output arguments becoming inputs).</p>
<p>Of course, you can also solve the exercise without explicit use of either of these two operators, just
remember that unification is implicitly performed with the predicate's arguments (head of clause).</p>
''',