[nongnu] elpa/csv2ledger 33a7db7844 157/190: Fix typo in the README

[ELPA Syncer]

branch: elpa/csv2ledger
commit 33a7db7844723f232f42bfc69f44a690de96db00
Author: Joost Kremers <joostkremers@fastmail.com>
Commit: Joost Kremers <joostkremers@fastmail.com>

    Fix typo in the README
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index bd3871f8dd..b588e45f6c 100644
--- a/README.md
+++ b/README.md
@@ -187,7 +187,7 @@ Another possible use of `c2l-field-modify-functions` is to 
make sure the value o
 
 ### Modifying the transaction ###
 
-One limitation of the functions in `c2l-field-modify-functions` is that they 
only take the value of a single field as argument. This is insufficient if you 
want to modify a field value on the basis of some other field or fields in the 
transaction, or if you want to add new fields. If you need to make such a 
change, you can add a function to the option 
`c2l-transaction-modify-functions`. This option holds a list of functions that 
take the entire transaction as its argument and return a mo [...]
+One limitation of the functions in `c2l-field-modify-functions` is that they 
only take the value of a single field as argument. This is insufficient if you 
want to modify a field value on the basis of some other field or fields in the 
transaction, or if you want to add new fields. If you need to make such a 
change, you can add a function to the option 
`c2l-transaction-modify-functions`. This option holds a list of functions that 
take the entire transaction as argument and return a modifi [...]
 
 The transaction is passed as an alist of field-value pairs, with the fields 
being symbols and the values being strings. For example, for the ledger entry 
shown above, the transaction would be as follows: