Add common mistakes sections to all function docs

Author: Marzogh

docs/api/functions/begin.md

@@ -25,6 +25,12 @@ Returns `true` on successful initialization and chip identification. Returns `fa
 
 Failure usually indicates wiring issues, wrong CS pin, unsupported chip, incorrect voltage levels, or SPI bus mismatch. Check `error(VERBOSE)` immediately.
 
+## Common Mistakes
+
+- Calling memory I/O before `begin()` has succeeded.
+- Passing a custom `flashChipSize` that does not match real hardware.
+- Ignoring a `false` return and continuing instead of checking `error(VERBOSE)`.
+
 ## Example
 
 ```cpp

docs/api/functions/constructors-spiflash.md

@@ -28,6 +28,12 @@ Constructors do not return values. They create the object and store interface co
 
 Misconfigured pins or bus selection are usually detected at `begin()` time via failed ID reads or error codes.
 
+## Common Mistakes
+
+- Using wrong CS pin relative to your wiring diagram.
+- Selecting alternate SPI bus constructor on a board/core that does not support it.
+- Passing custom SPI pin arrays that do not match board capabilities.
+
 ## Example
 
 ```cpp

docs/api/functions/constructors-spifram.md

@@ -26,6 +26,12 @@ Constructors do not return values; they prepare the instance.
 
 Incorrect bus/pin choices usually surface during `begin()` with zero IDs or non-zero error codes.
 
+## Common Mistakes
+
+- Using incorrect CS pin or alternate bus for your board wiring.
+- Assuming constructor validates wiring immediately (validation happens at `begin()`).
+- Reusing examples with different board pin numbering conventions without adjustment.
+
 ## Example
 
 ```cpp

docs/api/functions/eraseBlock32k.md

@@ -24,6 +24,12 @@ Returns `true` when erase completes.
 
 May fail on chips lacking 32 KB erase opcode or when write/ready checks fail.
 
+## Common Mistakes
+
+- Using 32 KB erase for tiny updates, causing unnecessary data loss.
+- Assuming all chips support 32 KB erase opcode.
+- Not preserving neighboring data in same erase block.
+
 ## Example
 
 ```cpp

docs/api/functions/eraseBlock64k.md

@@ -24,6 +24,12 @@ Returns `true` on success.
 
 Unsupported opcode/chip profile mismatch or bus errors can fail this call.
 
+## Common Mistakes
+
+- Erasing a 64 KB block when only a small region needed reset.
+- Failing to back up adjacent data in same block.
+- Treating block erase boundaries as page boundaries.
+
 ## Example
 
 ```cpp

docs/api/functions/eraseChip.md

@@ -25,6 +25,12 @@ Returns `true` when full erase/clear succeeds.
 
 Operation can be long on large flash chips. Power loss mid-operation may leave partially erased contents.
 
+## Common Mistakes
+
+- Running chip erase in normal flow instead of explicit maintenance/reset paths.
+- Not warning users that operation is destructive and long-running.
+- Power-cycling mid-erase and assuming data integrity afterwards.
+
 ## Example
 
 ```cpp

docs/api/functions/eraseSection.md

@@ -26,6 +26,12 @@ Returns `true` when clear operation completed successfully.
 
 Invalid ranges, protected states, busy chip state, or unsupported erase granularity can cause failure.
 
+## Common Mistakes
+
+- Erasing too small a region before rewriting larger payloads.
+- Assuming section erase aligns exactly to your object boundaries.
+- Not accounting for erase latency in time-sensitive loops.
+
 ## Example
 
 ```cpp

docs/api/functions/eraseSector.md

@@ -24,6 +24,12 @@ Returns `true` on successful sector erase.
 
 Fails if chip is busy, write-enable path fails, address invalid, or erase opcode unsupported.
 
+## Common Mistakes
+
+- Expecting arbitrary byte-range erase; this targets 4 KB sector granularity.
+- Erasing wrong sector by passing nearby but unintended address.
+- Not checking return code before writing new data.
+
 ## Example
 
 ```cpp

docs/api/functions/error.md

@@ -25,6 +25,12 @@ Returns numeric error code (`0` generally means no current error).
 
 Calling much later can hide root cause because newer operations may overwrite error context.
 
+## Common Mistakes
+
+- Reading `error()` long after the failing call, losing useful context.
+- Ignoring non-zero error values during early bring-up.
+- Using `error()` without `VERBOSE` while debugging first hardware setup.
+
 ## Example
 
 ```cpp

docs/api/functions/functionruntime.md

@@ -25,6 +25,12 @@ Returns elapsed runtime value of previous operation.
 
 Interpret values carefully: runtime depends on operation type, chip state, and diagnostic compile settings.
 
+## Common Mistakes
+
+- Comparing runtimes from different operation types directly.
+- Benchmarking with unstable wiring and reading too much into variance.
+- Forgetting that diagnostics/build settings can affect reported timing.
+
 ## Example
 
 ```cpp