From e7571e31b29a2b3dfc3451c2471e2ba349f88f58 Mon Sep 17 00:00:00 2001
From: hukla <129692708+huklaa@users.noreply.github.com>
Date: Wed, 12 Aug 2026 13:03:31 +0300
Subject: [PATCH] docs: align Part 2 verification claims with test

---
 docs/src/miden-bank/02-constants-constraints.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/src/miden-bank/02-constants-constraints.md b/docs/src/miden-bank/02-constants-constraints.md
index 2eb444f..7101b90 100644
--- a/docs/src/miden-bank/02-constants-constraints.md
+++ b/docs/src/miden-bank/02-constants-constraints.md
@@ -16,7 +16,7 @@ By the end of this section, you will have:
 - Used `assert!()` for transaction validation
 - Learned safe Felt comparison with `.as_canonical_u64()`
 - Added a deposit method skeleton with validation
-- **Verified constraints work** by testing that invalid operations fail
+- **Verified the constraint setup compiles** and the bank starts from the expected storage state
 
 ## Building on Part 1
 
@@ -260,7 +260,7 @@ miden build
 The Miden compiler prints non-fatal `MAST`-serialization `ERROR` lines on every build. These are cosmetic — the build still succeeds and emits the `.masp` package.
 :::
 
-## Optional: Verify Constraints Work
+## Optional: Verify Constraint Setup
 
 :::note
 This is an optional self-check. If you create this test file, you can run it to verify the contract compiles with the constraint logic. The main runnable tests begin in Part 4.