From b4501a270d102211d358b2c474af9f79ebc7b3b3 Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Thu, 19 Jan 2023 05:58:16 -1000 Subject: [PATCH] ;doc: csv: try to clarify how CSV fields and hledger fields work --- hledger/hledger.m4.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hledger/hledger.m4.md b/hledger/hledger.m4.md index 21dbbbe55..d696e88e6 100644 --- a/hledger/hledger.m4.md +++ b/hledger/hledger.m4.md @@ -3076,10 +3076,10 @@ Note the two kinds of "field names" used in hledger CSV rules: 2. **hledger field names** (`HLEDGERFIELD` in examples):\ These are special reserved names corresponding (directly or indirectly) to parts of a hledger transaction. If you use one of these names in a [`fields` list](#fields-list), or in a [field assignment](#field-assignment) rule, - it sets the value of some part of the hledger transaction corresponding the current CSV record, influencing the generated journal entry and hledger's output. + it sets the value of some part of the hledger transaction corresponding to the current CSV record, influencing the generated journal entry and hledger's output. Note these field names (both kinds) are used only in CSV rules files, -though the hledger field names correspond to the hledger transaction parts described in Journal > [Transactions](#transactions). +though the hledger field names correspond to the hledger transaction parts described in [hledger manual > Journal](#transactions). Here are the hledger field names available, and what happens when you assign values to them using a fields list or field assignment rule: