Minor tweaks and a missing location thanks to xabbuh and WouterJ

Author: weaverryan

cookbook/bundles/best_practices.rst

@@ -341,10 +341,15 @@ there are 3 modes, which the user can configure in their project:
 
 As a bundle author, you'll want to support *both* API's, since some users
 may still be using the 2.4 API. Specifically, if your bundle adds a violation
-directly to the :class:`Symfony\Component\Validator\Context\ExecutionContext`
+directly to the :class:`Symfony\\Component\\Validator\\Context\\ExecutionContext`
 (e.g. like in a custom validation constraint), you'll need to check for which
 API is being used. The following code, would work for *all* users::
 
+    use Symfony\Component\Validator\ConstraintValidator;
+    use Symfony\Component\Validator\Constraint;
+    use Symfony\Component\Validator\Context\ExecutionContextInterface;
+    // ...
+
     class ContainsAlphanumericValidator extends ConstraintValidator
     {
         public function validate($value, Constraint $constraint)

cookbook/form/unit_testing.rst

@@ -185,7 +185,7 @@ on other extensions. You need add those extensions to the factory object::
         {
             parent::setUp();
             
-            $validator = $this->getMock('\Symfony\Component\Validator\ValidatorInterface');
+            $validator = $this->getMock('\Symfony\Component\Validator\Validator\ValidatorInterface');
             $validator->method('validate')->will($this->returnValue(new ConstraintViolationList()));
 
             $this->factory = Forms::createFormFactoryBuilder()