docs: improve formatting and clarity in README features section

Author: tomerh2001

README.md

@@ -9,22 +9,29 @@ This project provides an importer from Israeli banks (via [israeli-bank-scrapers
 
 ## Features
 
-1. **Multi Bank Support**: Supports all of the institutions that the [israeli-bank-scrapers](https://github.com/eshaham/israeli-bank-scrapers) library covers (Bank Hapoalim, Cal, Leumi, Discount, etc.).
+1. **Multi Bank Support**  
+   Supports all of the institutions that the [israeli-bank-scrapers](https://github.com/eshaham/israeli-bank-scrapers) library covers (Bank Hapoalim, Cal, Leumi, Discount, etc.).
 
-2. **Prevents duplicate transactions** using Actual’s [`imported_id`](https://actualbudget.org/docs/api/reference/#transactions) logic.
+2. **Prevents duplicate transactions**  
+   Uses Actual’s [`imported_id`](https://actualbudget.org/docs/api/reference/#transactions) logic.
 
-3. **Automatic Account Creation**: If the bank account does not exist in Actual, it will be created automatically.
+3. **Automatic Account Creation**  
+   If the bank account does not exist in Actual, it will be created automatically.
 
-4. **Reconciliation:** Optional reconciliation to adjust account balances automatically.
+4. **Reconciliation**  
+   Optional reconciliation to adjust account balances automatically.
 
-5. **Credit Card / Multi-Account Mapping (Targets):** Supports mapping multiple scraped accounts/cards into one Actual account, or mapping each scraped card into its own Actual account (via `targets` and `accounts`).
+5. **Credit Card / Multi-Account Mapping (Targets)**  
+   Supports mapping multiple scraped accounts/cards into one Actual account, or mapping each scraped card into its own Actual account (via `targets` and `accounts`).
 
-6. **Concurrent Processing:** Uses a queue (via [p-queue](https://www.npmjs.com/package/p-queue)) to manage scraping tasks concurrently.
+6. **Concurrent Processing**  
+   Uses a queue (via [p-queue](https://www.npmjs.com/package/p-queue)) to manage scraping tasks concurrently.
 
 ## Installation
 
 ### Docker
 https://hub.docker.com/r/tomerh2001/israeli-banks-actual-budget-importer
+
 #### Example
 ```yml
 services:
@@ -44,18 +51,18 @@ services:
 
 ## Configuration
 
-The application configuration is defined using JSON and validated against a schema.
+The application configuration is defined using JSON and validated against a schema.  
 The main configuration file is `config.json`.
 
 The configuration has **two independent top-level sections**:
-1. `actual`: Configures the Actual Budget connection.
-2. `banks`: Configures bank scrapers and account mappings.
+1. `actual` – Configures the Actual Budget connection.
+2. `banks` – Configures bank scrapers and account mappings.
 
 ---
 
 ### 1) `actual` section
 
-This section configures the connection to your Actual Budget server and budget.
+This section configures the connection to your Actual Budget server and budget.  
 It is **always required**, regardless of how you configure banks or targets.
 
 ```json
@@ -86,11 +93,13 @@ The `banks` section defines:
 - How scraped accounts/cards are mapped into Actual accounts
 
 Each bank entry includes the credentials required by `israeli-bank-scrapers`
-(e.g. `userCode`, `username`, `password`, etc.) and supports **multiple mapping modes**.
+(e.g. `userCode`, `username`, `password`, etc.).
+
+---
 
-#### `targets` sub-section
+### `targets` sub-section
 
-A single bank scrape (for example `visaCal`) may return **multiple accounts/cards**.
+A single bank scrape (for example `visaCal`) may return **multiple accounts/cards**.  
 Different users model these differently in Actual, so the importer supports `targets`.
 
 Each **target** represents:
@@ -99,27 +108,21 @@ Each **target** represents:
 
 For each target:
 - Imported transactions = concatenation of transactions from selected cards
-- Reconciliation (if enabled) = sum of balances of selected cards
+- Reconciliation (if enabled) = sum of balances of selected cards  
   (only cards with a valid numeric balance are included)
 
 ---
 
-#### Reconciliation modes
+### Reconciliation behavior
 
-The `reconcile` field can be configured per bank (legacy mapping) or per target.
-
-Supported values:
-- `false` (or omitted): no reconciliation transaction is created/updated.
-- `true`: reconciliation is created/updated **per target** (recommended when multiple targets share the same `actualAccountId`).
-- `"consolidate"`: reconciliation is created/updated **consolidated per Actual account** (one reconciliation transaction per `actualAccountId`).
-
-Notes:
-- In **legacy** (single-account) configs, `reconcile: true` behaves like `"consolidate"` for backward compatibility.
-- In `targets` configs, `reconcile: true` is per-target and does not collide across multiple targets that map into the same Actual account.
+- Reconciliation is controlled by the `reconcile` boolean.
+- When `reconcile: true`, **a new reconciliation transaction is created on every run** (no updates, no reconciliation).
+- Existing reconciliation transactions are never modified or reused.
+- If `reconcile` is omitted or set to `false`, no reconciliation transaction is created.
 
 ---
 
-#### Example A: One Actual account for all VisaCal cards (consolidated)
+### Example A: One Actual account for all VisaCal cards
 
 ```json
 {
@@ -141,7 +144,7 @@ Notes:
       "targets": [
         {
           "actualAccountId": "actual-creditcards-all",
-          "reconcile": "consolidate",
+          "reconcile": true,
           "accounts": "all"
         }
       ]
@@ -152,7 +155,7 @@ Notes:
 
 ---
 
-#### Example B: One Actual account per VisaCal card (separate accounts)
+### Example B: One Actual account per VisaCal card
 
 ```json
 {
@@ -190,7 +193,7 @@ Notes:
 
 ---
 
-#### Example C: Grouped cards into a single Actual account (subset)
+### Example C: Grouped cards into a single Actual account (subset)
 
 ```json
 {
@@ -223,56 +226,13 @@ Notes:
 
 ---
 
-#### Example D: Multiple targets importing into the same Actual account (safe per-target reconciliation)
-
-Use `reconcile: true` so each target maintains its own reconciliation transaction (no overwrites).
-
-```json
-{
-  "actual": {
-    "init": {
-      "dataDir": "./data",
-      "password": "your_actual_password",
-      "serverURL": "https://your-actual-server.com"
-    },
-    "budget": {
-      "syncId": "your_sync_id",
-      "password": "your_budget_password"
-    }
-  },
-  "banks": {
-    "visaCal": {
-      "username": "bank_username",
-      "password": "bank_password",
-      "targets": [
-        {
-          "actualAccountId": "actual-cal-all",
-          "reconcile": true,
-          "accounts": ["8538"]
-        },
-        {
-          "actualAccountId": "actual-cal-all",
-          "reconcile": true,
-          "accounts": ["7697"]
-        }
-      ]
-    }
-  }
-}
-```
-
----
-
 ## Legacy configuration (single Actual account per bank)
 
-This configuration style is **fully supported for backward compatibility**,
+This configuration style is **fully supported for backward compatibility**,  
 but does **not** allow fine-grained control over multiple cards/accounts.
 
 It maps all scraped accounts from the bank into a single Actual account.
 
-Important:
-- `reconcile: true` in legacy configs behaves like `reconcile: "consolidate"`.
-
 ```json
 {
   "actual": {
@@ -319,5 +279,4 @@ This project is open-source. Please see the [LICENSE](./LICENSE) file for licens
 
 - **israeli-bank-scrapers:** Thanks to the contributors of the bank scraper libraries.
 - **Actual App:** For providing a powerful budgeting API.
-- **Open-source Community:** Your support and contributions are appreciated.
-- 
+- **Open-source Community:** Your support and contributions are appreciated.