Add information about the erlang.mk plugin
diff --git a/README.org b/README.org
index 8003d1c..e81fb03 100644
--- a/README.org
+++ b/README.org
@@ -39,8 +39,9 @@
the attribute =-triq(eunit)= will generate EUnit tests for all
properties, turning the module into a regular EUnit test suite.
-We highly recommend letting Triq generate EUnit tests, thus arriving
-at a demo module like this:
+If you use erlang.mk, you will typically want to use [[https://erlang.mk/guide/triq.html][the built-in Triq
+plugin]] to check properties. Otherwise we highly recommend letting Triq
+generate EUnit tests, thus arriving at a demo module like this:
#+BEGIN_EXAMPLE erlang
-module(triq_demo).
diff --git a/doc/overview.edoc b/doc/overview.edoc
index 9e8f59e..204004d 100644
--- a/doc/overview.edoc
+++ b/doc/overview.edoc
@@ -2,10 +2,11 @@
@copyright 2010 Trifork A/S
@doc Triq is a QuickCheck library for Erlang that works similar to PropEr and
QuviQ eqc. The easiest way to integrate it in your tests is to write properties
-as you're used, replace the header include with that of triq, and then add the
-<tt>-triq(eunit).</tt> attribute in the module. This will generate the needed
-EUnit glue in order to test the properties anytime you run EUnit. If you use
-<tt>-triq({eunit, [{runs, N}]})</tt>, then Triq will do <tt>N</tt> runs for
-each property in the module, which is equivalent to calling
+as you're used, replace the header include with that of triq, and either use <a
+href="https://erlang.mk/guide/triq.html">the Triq plugin for erlang.mk</a> or
+add the <tt>-triq(eunit).</tt> attribute in the module. The latter will generate
+the needed EUnit glue in order to test the properties anytime you run EUnit. If
+you use <tt>-triq({eunit, [{runs, N}]})</tt>, then Triq will do <tt>N</tt> runs
+for each property in the module, which is equivalent to calling
<tt>triq:check(Module, N)</tt>. This can be useful to make Triq try more (or
less) cases than the default.
