diff --git a/docs/source/rename_map.mdx b/docs/source/rename_map.mdx
index 6249faaca..16ee6344a 100644
--- a/docs/source/rename_map.mdx
+++ b/docs/source/rename_map.mdx
@@ -61,17 +61,6 @@ lerobot-eval \
   --rename_map='{"observation.images.image": "observation.images.base_0_rgb", "observation.images.image2": "observation.images.left_wrist_0_rgb"}'
 ```
 
-### Recording
-
-`lerobot-record` also supports rename maps, nested under the dataset config:
-
-```bash
-lerobot-record \ # When running inference
-  --policy.path="<user>/smolVLA_finetuned" \
-  ... \
-  --dataset.rename_map='{"observation.images.glove2": "observation.images.image"}'
-```
-
 ## Alternative: edit the policy config directly
 
 If you always use the same dataset or environment, you can **edit the policy's `config.json`** so its observation keys match your data source. Then no rename map is needed.
@@ -105,10 +94,10 @@ XVLA-base has three visual inputs and `empty_cameras=0` by default. Your dataset
 
 ## Quick reference
 
-| Goal                                      | What to do                                                                  |
-| ----------------------------------------- | --------------------------------------------------------------------------- |
-| Dataset keys ≠ policy keys                | `--rename_map='{"dataset_key": "policy_key", ...}'`                         |
-| Env keys ≠ policy keys (eval)             | `--rename_map='{"env_key": "policy_key", ...}'`                             |
-| Recording with different keys (inference) | `--dataset.rename_map='{"source_key": "policy_key", ...}'`.                 |
-| Fewer cameras than policy expects         | `--policy.empty_cameras=N` (supported by PI0, PI05, PI0Fast, SmolVLA, XVLA) |
-| Avoid passing a rename map                | Edit the policy's `config.json` so its keys match your data source          |
+| Goal                                    | What to do                                                                  |
+| --------------------------------------- | --------------------------------------------------------------------------- |
+| Dataset keys ≠ policy keys              | `--rename_map='{"dataset_key": "policy_key", ...}'`                         |
+| Env keys ≠ policy keys (eval)           | `--rename_map='{"env_key": "policy_key", ...}'`                             |
+| Rollout with different keys (inference) | `--rename_map='{"source_key": "policy_key", ...}'`.                         |
+| Fewer cameras than policy expects       | `--policy.empty_cameras=N` (supported by PI0, PI05, PI0Fast, SmolVLA, XVLA) |
+| Avoid passing a rename map              | Edit the policy's `config.json` so its keys match your data source          |
diff --git a/src/lerobot/rollout/configs.py b/src/lerobot/rollout/configs.py
index f74baa781..2ee3122dc 100644
--- a/src/lerobot/rollout/configs.py
+++ b/src/lerobot/rollout/configs.py
@@ -289,9 +289,8 @@ class RolloutConfig:
             raise ValueError("--policy.path is required for rollout")
 
         # --- Task resolution ---
-        # When --dataset.rename_map (or any --dataset.* flag) is passed, draccus
-        # creates a DatasetRecordConfig with single_task="".  If the user set
-        # the task via the top-level --task flag, propagate it so that all
+        # When any --dataset.* flag is passed, draccus creates a DatasetRecordConfig with single_task="".
+        # If the user set the task via the top-level --task flag, propagate it so that all
         # downstream consumers (inference engine, dataset frame builders) see it.
         if self.dataset is not None and not self.dataset.single_task and self.task:
             logger.info("Propagating top-level task '%s' to dataset config", self.task)