@@ -160,9 +160,9 @@ errorPath
160160..versionadded ::2.1
161161 The ``errorPath `` option was added in Symfony 2.1.
162162
163- If the entity violatesagainst this constraint the error message is bound to
164- the first field . If there are more than one fields it maybe desired tobind the
165- error message to another field.
163+ If the entity violates constraint the error message is bound to the first
164+ field in ` fields `_ . If there are more than one fields, you maywant tomap
165+ the error message to another field.
166166
167167Consider this example:
168168
@@ -174,7 +174,7 @@ Consider this example:
174174Acme\AdministrationBundle\Entity\Service :
175175constraints :
176176 -Symfony\Bridge\Doctrine\Validator\Constraints\UniqueEntity :
177- fields :[ host, port ]
177+ fields :[host, port]
178178errorPath :port
179179message :' This port is already in use on that host.'
180180
@@ -251,7 +251,7 @@ Consider this example:
251251 }
252252 }
253253
254- Now, the message would be bound to theform field of the ``port `` with this configuration.
254+ Now, the message would be bound to the ``port `` field with this configuration.
255255
256256
257257ignoreNull
@@ -266,6 +266,3 @@ If this option is set to ``true``, then the constraint will allow multiple
266266entities to have a ``null `` value for a field without failing validation.
267267If set to ``false ``, only one ``null `` value is allowed - if a second entity
268268also has a ``null `` value, validation would fail.
269-
270-
271- .. _`field` : `fields `_