diff --git a/docs/ref/models/constraints.txt b/docs/ref/models/constraints.txt
index aaadc78ee9..d172353326 100644
--- a/docs/ref/models/constraints.txt
+++ b/docs/ref/models/constraints.txt
@@ -30,10 +30,10 @@ option.
 
 .. admonition:: Validation of Constraints
 
-    In general constraints are **not** checked during ``full_clean()``, and do
-    not raise ``ValidationError``\s. Rather you'll get a database integrity
+    In general constraints are **not** checked during ``full_clean()``, and do
+    not raise ``ValidationError``\s. Rather you'll get a database integrity
     error on ``save()``. ``UniqueConstraint``\s are different in this regard,
-    in that they leverage the existing ``validate_unique()`` logic, and thus
+    in that they leverage the existing ``validate_unique()`` logic, and thus
     enable two-stage validation. In addition to ``IntegrityError`` on
     ``save()``, ``ValidationError`` is also raised during model validation when
     the ``UniqueConstraint`` is violated.