minor #12712 Tweak the IsTrue validation docs (javiereguiluz)

javiereguiluz · javiereguiluz · commit a9cfb3a57eb7 · 2019-11-30T17:58:31.000+01:00
This PR was squashed before being merged into the 3.4 branch (closes #12712). Discussion ---------- Tweak the IsTrue validation docs Please review that this is correct: *IsTrue requires that method names start with "is" or "get"* Thanks! Commits ------- c47d8ae Tweak the IsTrue validation docs
diff --git a/reference/constraints/IsTrue.rst b/reference/constraints/IsTrue.rst
@@ -1,9 +1,8 @@
 IsTrue
 ======
 
-Validates that a value is ``true``. Specifically, this checks to see if
-the value is exactly ``true``, exactly the integer ``1``, or exactly the
-string "``1``".
+Validates that a value is ``true``. Specifically, this checks if the value is
+exactly ``true``, exactly the integer ``1``, or exactly the string ``"1"``.
 
 Also see :doc:`IsFalse <IsFalse>`.
 
@@ -23,9 +22,9 @@ Basic Usage
 -----------
 
 This constraint can be applied to properties (e.g. a ``termsAccepted`` property
-on a registration model) or to a "getter" method. It's most powerful in
-the latter case, where you can assert that a method returns a true value.
-For example, suppose you have the following method::
+on a registration model) and methods. It's most powerful in the latter case,
+where you can assert that a method returns a true value. For example, suppose
+you have the following method::
 
     // src/AppBundle/Entity/Author.php
     namespace AppBundle\Entity;
@@ -40,7 +39,7 @@ For example, suppose you have the following method::
         }
     }
 
-Then you can constrain this method with ``IsTrue``.
+Then you can validate this method with ``IsTrue`` as follows:
 
 .. configuration-block::
 
