# HG changeset patch
# User Raphaël Gomès <rgomes@octobus.net>
# Date 1736951342 -3600
#      Wed Jan 15 15:29:02 2025 +0100
# Node ID 62e0b9c6429d568959839b733e8a3fe3f2d9ea6c
# Parent  a44423d8859a8cce5f7f7192c2717f720b85ad1f
docs: slight improvements to the den docs

diff --git a/docs/poulpe-den.md b/docs/poulpe-den.md
--- a/docs/poulpe-den.md
+++ b/docs/poulpe-den.md
@@ -38,15 +38,18 @@
 
 The first and most manual thing about Poulpe is setting up data environments,
 since they are specific to what you are actually trying to benchmark.
-(See their section in docs/concept.rst)
+(See their section in [concept.md](concept.md))
 
 In the following example, we will look at the suite for benchmarking Mercurial.
+To do this, we need at least one Mercurial repository to run our tests on.
 
   ```shell
   # inside the poulpe den folder, with the virtualenv active
   $ mkdir data-envs/my-repo
+  # `main` is the default path for the reference of the repo to test inside
+  # the data-env
   $ hg clone /path/to/my-repo data-envs/my-repo/main
-  $ ./suites/hg/data-end-setup/setup-full.py data-envs/my-repo
+  $ ./suites/hg/data-env-setup/setup-full.py data-envs/my-repo
   [...]
 
   # You can check that the den sees the new environment