From d79573d950719a52ff15ec37e772e36a0280e600 Mon Sep 17 00:00:00 2001 From: Yann Hamdaoui Date: Fri, 18 Feb 2022 16:23:39 +0100 Subject: [PATCH] Update doc/manual/contracts.md Co-authored-by: Arnaud Spiwack --- doc/manual/contracts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/manual/contracts.md b/doc/manual/contracts.md index aa02dc8f..890a1445 100644 --- a/doc/manual/contracts.md +++ b/doc/manual/contracts.md @@ -67,7 +67,7 @@ A custom contract is a function of two arguments: - A `label`. Provided by the interpreter, the label contains tracking information for error reporting. Its main usage is to be passed to `contracts.blame` or `contracts.blame_with` when the contract isn't satisfied. -- The tested value. +- The value being checked. Upon success, the contract must return the original value. It may seem strange and kinda pointless for now, but we will see the motivation behind this design