From f148eec5fb5e6701f14059fa4b984f8cb0934b28 Mon Sep 17 00:00:00 2001
From: Simon Michael <simon@joyful.com>
Date: Fri, 6 Dec 2024 07:13:03 -1000
Subject: [PATCH] ;doc:query types: edits

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

diff --git a/hledger/hledger.m4.md b/hledger/hledger.m4.md
index 89ec2b19d..6c69bc98c 100644
--- a/hledger/hledger.m4.md
+++ b/hledger/hledger.m4.md
@@ -5225,9 +5225,8 @@ Match by transaction code (eg check number).
 Match postings or transactions including any amounts whose currency/commodity symbol is fully matched by REGEX.
 (Contrary to hledger's usual infix matching. To do infix matching, write `.*REGEX.*`.) 
 Note, to match [special characters](#special-characters) which are regex-significant, you need to escape them with `\`.
-And for characters which are significant to your shell you may need one more level of escaping. 
-So eg to match the dollar sign:\
-`hledger print cur:\\$`.
+And for characters which are significant to your shell you will usually need one more level of escaping.
+Eg to match the dollar sign: `cur:\\$` or `cur:'\$'`
 
 ### desc: query
 **`desc:REGEX`**\
@@ -5293,6 +5292,7 @@ Certain kinds of account alias can disrupt account types, see
 ### tag: query
 **`tag:NAMEREGEX[=VALREGEX]`**\
 Match by tag name, and optionally also by tag value. Note:
+
 - To match values, ignoring names, do `tag:.=VALREGEX`
 - Both regular expressions do infix matching by default.
   If you need a complete match, use `^` and `$`.