docs: update manual and faq with latest balance assertions info

FAQ.md

@@ -195,6 +195,11 @@ comments may be permissible in different places.
 - hledger's [include directive](MANUAL.html#including-other-files) does not support
   shell glob patterns (eg `include *.journal` ), which ledger does.
 
+- when checking [balance assertions](MANUAL.html#balance-assertions)
+  hledger sorts the account's postings first by date and then (for
+  postings with the same date) by parse order. ledger goes strictly by
+  parse order.
+
 ### How are the implementations different ?
 
 ledger is written in C++, whereas hledger is written in the

MANUAL.md

@@ -263,11 +263,16 @@ each posting:
 After reading a journal file, hledger will check all balance
 assertions and report an error if any of them fail. Balance assertions
 can protect you from, eg, inadvertently disrupting reconciled balances
-while cleaning up old entries. Some tips:
+while cleaning up old entries.
 
-- balance assertions depend on the order postings are parsed from the file(s). The posting's date is ignored, currently.
+Note, when checking balance assertions hledger sorts the account's
-- balance assertion amounts currently must have a commodity symbol.
+postings first by date and then (for postings with the same date) by
-- balance assertions' impact on parsing time for large files is not yet known.
+parse order. This is different from ledger, which currently goes
+strictly by parse order. Sorting by date means balance assertions will
+still work if you reorder your entries.
+
+The impact of balance assertions on parsing time for large files is
+not yet known.
 
 #### Prices