markdown: minor tweak of intro scope

"financial world" implies larger scope of finances (including analysis).

markdown/How-do-I-get-started.md

@@ -25,7 +25,7 @@
 
 ## How do I get started?
 
-docker-finance (`dfi`) is not your typical Docker image in which you simply pull and containerize: `dfi` is an *image-based* accounting system that operates translucently between your client (host) and container; keeping your financial world containerized (and with all the benefits of containerization).
+docker-finance (`dfi`) is not your typical Docker image in which you simply pull and containerize. `dfi` is an *image-based* accounting system that operates translucently between your client (host) and container; keeping your financial world containerized (and with all the benefits of containerization).
 
 To get started, you'll only need a modern Linux client (host) with a working Docker installation.
 
@@ -64,7 +64,7 @@ To get started, you'll only need a modern Linux client (host) with a working Doc
      ```bash
      # NOTE: you can change the domain to `gitea.com`, as this repository is also mirrored there
      if hash git &>/dev/null; then
-       if ! git clone --depth=1 https://gitea.evergreencrypto.co/EvergreenCrypto/docker-finance docker-finance/repo -b v1.4.1; then
+       if ! git clone --depth=1 https://gitea.evergreencrypto.co/EvergreenCrypto/docker-finance docker-finance/repo -b v1.3.0; then
            echo "FATAL: docker-finance repo not cloned" >&2
        fi
      else

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

@@ -372,14 +372,6 @@ Your `flow` directory will contain a symlink called `src` which links to code th
 
 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!**
 
-##### Caveats & Oddities: Flow: Accounts: Ledger
-
-In the "Ledger Live" desktop app, change your wallet name to reflect your subaccount(s). They SHOULD be named with the format: `device_supertype:device_subtype:wallet_name-counter` in order to future-proof the number of devices and wallets that have the same name. For example:
-
-   1. You have 1 Ledger Nano S device with 2 bitcoin wallets ("spending" and "savings"). They would be named `nano:s-1:spending-1` and `nano:s-1:savings-1`
-   2. You have 1 Ledger Nano X device with 1 bitcoin wallet ("spending") and 1 ethereum wallet ("staking"). They would be named `nano:x-1:spending-1` and `nano:x-1:staking-1`
-   > Note: you can reuse "Ledger Live" wallet names across all chains because chains and symbols are added internally through `dfi` (i.e., you can name your bitcoin and ethereum wallets both `nano:x-1:spending-1`
-
 ##### 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: