From 12c8e0a418e68d8b8f79a0d526041086d798f686 Mon Sep 17 00:00:00 2001 From: Carlos Granados Date: Sun, 11 Oct 2015 14:12:44 +0200 Subject: [PATCH] Misspelling It should be "were" instead of "where". But I think it is even better to use the present tense here, so I changed it to "is" --- reference/constraints/UniqueEntity.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/constraints/UniqueEntity.rst b/reference/constraints/UniqueEntity.rst index 7974d3ac0fd..7606c44ac94 100644 --- a/reference/constraints/UniqueEntity.rst +++ b/reference/constraints/UniqueEntity.rst @@ -121,7 +121,7 @@ fields This required option is the field (or list of fields) on which this entity should be unique. For example, if you specified both the ``email`` and ``name`` field in a single ``UniqueEntity`` constraint, then it would enforce that -the combination value where unique (e.g. two users could have the same email, +the combination value is unique (e.g. two users could have the same email, as long as they don't have the same name also). If you need to require two fields to be individually unique (e.g. a unique