make hittekaart available by default

1 files changed, 5 insertions, 9 deletions

diff --git a/doc/administration/configuration.rst b/doc/administration/configuration.rst
index 24c5fdb..98f3592 100644
--- a/doc/administration/configuration.rst
+++ b/doc/administration/configuration.rst
@@ -221,15 +221,12 @@ true``. This will cause the tiles to be loaded directly by the client.
 Hittekaart Integration
 ----------------------
 
-Fietsboek can use hittekaart_ to generate heat maps for users. For that, you
-can set ``hittekaart.bin`` to the path to the ``hittekaart`` binary. If unset,
-it is assumed that the binary can be found in your ``$PATH``.
+Fietsboek can use hittekaart_ to generate heat maps for users.
 
-In addition, you can set ``hittekaart.autogenerate`` to the list of overlay
-maps you want to automatically generate and update. By default, this list is
-empty, which means that Fietsboek will not generate any overlays on its own.
-You can add ``heatmap`` and/or ``tilehunter`` to generate those maps
-automatically.
+You can set ``hittekaart.autogenerate`` to the list of overlay maps you want to
+automatically generate and update. By default, this list is empty, which means
+that Fietsboek will not generate any overlays on its own. You can add
+``heatmap`` and/or ``tilehunter`` to generate those maps automatically.
 
 By default, ``hittekaart`` will use as many threads as CPU cores are available.
 This leads to the fastest heatmap generation, but might be undesired on shared
@@ -253,7 +250,6 @@ An example configuration excerpt can look like this:
 
 .. code-block:: ini
 
-    hittekaart.bin = /usr/local/bin/hittekaart
     hittekaart.autogenerate = heatmap tilehunter
     hittekaart.threads = 2