Update README.

1 files changed, 1 insertions, 1 deletions

diff --git a/README.md b/README.md
index 943a166..11deb34 100644
--- a/README.md
+++ b/README.md
@@ -22,7 +22,7 @@ Especially relevant for the purpose of this library is that there are difference
 
 In CSL-JSON data, the format of the alist is slightly different: `<field>` is not a string but a symbol and the symbol name is case-sensitive. The CSL-JSON standard describes which field names are lower case (most are) and which are upper case (`ISBN`, `DOI`, etc.) Furthermore, the `<value>` part of the alist items may be a string, a number or a vector, though when parsing a `.json` file, you can have `parsebib` convert all values to strings.
 
-You can access the data in an entry's alist with `assoc` or `alist-get`, but in order to accommodate for the differences, you may want to write a custom `test` function to pass to them, so that you can generalise over the field name type.
+You can access the data in an entry's alist with `assoc` or `alist-get`, but in order to accommodate for the differences, you may want to use `assoc-string` instead, which generalises over symbols and stings and has a `case-fold` argument.
 
 Another thing to note is that in BibTeX data, the type and key of an entry are stored in the entry's alist under `=type=` and `=key=`, while the same information is available in CSL-JSON data under `type` and `id`, respectively. While some of the core information on an entry is available in fields with the same name in both formats (esp. author, editor and title), most fields are named differently (i.e.., the `year` field in BibTeX corresponds to the `issued` field in CSL-JSON).