markdown: update Caveats & Oddities headers (for links)

markdown/How-do-I-use-it.md

@@ -1,7 +1,7 @@
 
 [//]: # (docker-finance | modern accounting for the power-user)
 [//]: # ()
-[//]: # (Copyright [C] 2021-2025 Aaron Fiore [Founder, Evergreen Crypto LLC])
+[//]: # (Copyright [C] 2021-2026 Aaron Fiore [Founder, Evergreen Crypto LLC])
 [//]: # ()
 [//]: # (This program is free software: you can redistribute it and/or modify)
 [//]: # (it under the terms of the GNU General Public License as published by)
@@ -169,15 +169,15 @@ See the container `times help` command for details.
 
 ### Caveats & Oddities
 
-#### Flow Layout
+#### Caveats & Oddities: Flow
 
 Your `flow` directory will contain a symlink called `src` which links to code that processes your data. **Do not delete this symlink**.
 
-##### *Prices*
+##### Caveats & Oddities: Flow: Prices
 
 Before you try to infer market prices, be sure to fetch prices *before* you do your first import (or first import of the year). If you do not fetch, the prices journal will **not** be included within the import and, if you have a previous year of prices, **you will unwittingly infer against that previous year instead of your expected year!**
 
-##### *Accounts: Trezor*
+##### Caveats & Oddities: Flow: Accounts: Trezor
 
 In the "Trezor Suite" app, change your wallet name to your subaccount(s). For example, to delineate between your Trezor One from several Trezor T devices, and to delineate between their separate wallets *within* every device, follow these steps:
 
@@ -194,7 +194,7 @@ docker-finance relies on `Amount unit` within the file for the actual symbol/cur
   1. This allows you to maintain device continuity by reusing wallet names for different currencies.
   2. This allows you to export, in the future, to the correct file from the associated hardware wallet because each hardware wallet exports its own unique CSV.
 
-#### Taxes
+##### Caveats & Oddities: Flow: Taxes
 
 - If you have a wallets designated for `SPEND`ing/`GIFT`ing or `INCOME`, you can use custom rules to mark all outgoing/incoming transactions as such (ex., using tags `taxed_as:SPEND`/`taxed_as:GIFT`/`taxed_as:INCOME`/etc.). See implementation for details.
 - **WARNING**: *all* `GIFTIN` cost-basis must be manually entered from the corresponding `GIFT` results/calculations (as gifted from another).