From 5c3197dd422f5d852a44a03e8e78f432777e3c2a Mon Sep 17 00:00:00 2001
From: Simon Michael <simon@joyful.com>
Date: Wed, 16 Apr 2025 16:29:53 -1000
Subject: [PATCH] ;doc:csv: How CSV rules are evaluated: clarify

---
 hledger/hledger.m4.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/hledger/hledger.m4.md b/hledger/hledger.m4.md
index 8bb64724c..93ba9dcc3 100644
--- a/hledger/hledger.m4.md
+++ b/hledger/hledger.m4.md
@@ -4255,7 +4255,8 @@ If you get a confusing error while reading a CSV file, it may help to try to und
 1. Any [included](#include) rules files are inlined, from top to bottom, depth first
    (scanning each included file for further includes, recursively, before proceeding).
 
-2. Top level rules (`date-format`, `fields`, `newest-first`, `skip` at top level, etc) are processed, top to bottom.
+2. Top level rules (`date-format`, `fields`, `newest-first`, `skip` at top level, etc)
+   are read, top to bottom.
    If a rule occurs more than once, the last one wins;
    except for `skip`/`end` rules, where the first one wins.