From aa898eb9a2659b365ca000b159f7f0daafb9c26e Mon Sep 17 00:00:00 2001 From: mat007 Date: Sun, 27 Jan 2013 17:52:17 +0000 Subject: [PATCH] Fixed typo in documentation git-svn-id: https://svn.code.sf.net/p/turtle/code/trunk@591 860be788-9bd5-4423-9f1e-828f051e677b --- build/boost/doc/customisation.qbk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build/boost/doc/customisation.qbk b/build/boost/doc/customisation.qbk index 2782fd9..6020120 100644 --- a/build/boost/doc/customisation.qbk +++ b/build/boost/doc/customisation.qbk @@ -46,7 +46,7 @@ The interesting part is the call to mock::format which enables the whole can-be- A constraint provides a means to validate a parameter received in a call to a mock object. -The library comes with a set of pre-defined [link turtle.reference.expectation.constraints]] matching the most widely used cases, however it is quite common to need to perform a custom validation. +The library comes with a set of pre-defined [link turtle.reference.expectation.constraints constraints] matching the most widely used cases, however it is quite common to need to perform a custom validation. Creating a constraint can be as simple as writing a function, for instance :