Add fixes

Signed-off-by: AkramBitar <akram@il.ibm.com>

Author: AkramBitar

docs/configuration.md

@@ -615,8 +615,8 @@ token:
     maxPageSize: 1000
 ```
 
-See [Transaction Store API Bounds](services/storage/api-bounds.md) for details,
-including why movement/balance queries are intentionally not row-capped.
+See [Transaction Store API Limits](services/storage.md#transaction-store-api-limits)
+for details, including why movement/balance queries are intentionally not row-capped.
 
 ---
 

docs/services/storage.md

@@ -315,9 +315,28 @@ Cleanup behavior is controlled by the configuration section. See the [Configurat
 
 See the [Configuration Guide](../configuration.md), Section `Optional: token.tms.<name>.services.network.fabric.recovery`, for detailed parameter descriptions and tuning recommendations.
 
-## Transaction Store API Bounds
-
-The transaction store enforces upper bounds on its write and read paths (maximum
-serialised write payload, mandatory bounded pagination on transaction queries,
-and a hard cap on token-request queries) so a single oversized write or unbounded
-scan cannot monopolise database resources. See [**Transaction Store API Bounds**](storage/api-bounds.md).
+## Transaction Store API Limits
+
+The transaction store (used by both **TTXDB** and **AuditDB**) limits its writes and
+reads so one huge write or one runaway query can't eat up the database. The checks
+live in the single SQL implementation
+(`token/services/storage/db/sql/common/transactions.go`), so the owner and auditor
+stores are both covered.
+
+**Write size limit.** `AddTokenRequest`, `AddTransaction`, and `AddMovement` reject a
+call whose payload is larger than `maxPayloadSize` (default 4 MiB; `0` turns the check
+off). `AddTokenRequest` measures the raw token request plus its metadata;
+transaction and movement records add up their field lengths instead, to keep the
+write path fast.
+
+**Read size limits.** `QueryTransactions` needs a bounded page argument (`nil` and
+`pagination.None()` are rejected; callers page through the full result set).
+`QueryTokenRequests` adds a hard `LIMIT` equal to `maxPageSize` (default 1000).
+`QueryMovements` is left uncapped on purpose: it feeds balance totals, and dropping
+rows there would quietly return wrong balances. It is already narrowed by its required
+filters.
+
+Both limits have built-in defaults. You can override them in configuration
+(`token.storage.maxPayloadSize` / `maxPageSize`) or in code with the
+`WithMaxPayloadSize` / `WithMaxPageSize` store options. See the
+[Configuration Guide](../configuration.md) for the config keys.