diff --git a/hledger/hledger.m4.md b/hledger/hledger.m4.md index a1c9e178c..baba326ae 100644 --- a/hledger/hledger.m4.md +++ b/hledger/hledger.m4.md @@ -2857,12 +2857,10 @@ layout, date format etc.), how to construct hledger transactions from it, and how to categorise transactions based on description or other attributes. -By default hledger looks for a rules file named like the CSV file with -an extra `.rules` extension, in the same directory. Eg when asked to -read `foo/FILE.csv`, hledger looks for `foo/FILE.csv.rules`. +By default, hledger expects this rules file to be named like the CSV file, +with an extra `.rules` extension added, in the same directory. +Eg when asked to read `foo/FILE.csv`, hledger looks for `foo/FILE.csv.rules`. You can specify a different rules file with the `--rules-file` option. -If no rules file is found, hledger will create a sample rules file, -which you'll need to adjust. At minimum, the rules file must identify the date and amount fields, and often it also specifies the date format and how many header lines