minor #15955 [Form] Minor fixes (sebpacz)

This PR was merged into the 4.4 branch.

Discussion
----------

[Form] Minor fixes

I found two comments that point to the wrong variable.

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/releases for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `5.x` for features of unreleased versions).

-->

Commits
-------

9cb23a5 [Form] Minor fixes

Author: javiereguiluz

form/unit_testing.rst

@@ -55,7 +55,7 @@ The simplest ``TypeTestCase`` implementation looks like the following::
             ];
 
             $model = new TestObject();
-            // $formData will retrieve data from the form submission; pass it as the second argument
+            // $model will retrieve data from the form submission; pass it as the second argument
             $form = $this->factory->create(TestedType::class, $model);
 
             $expected = new TestObject();
@@ -67,7 +67,7 @@ The simplest ``TypeTestCase`` implementation looks like the following::
             // This check ensures there are no transformation failures
             $this->assertTrue($form->isSynchronized());
 
-            // check that $formData was modified as expected when the form was submitted
+            // check that $model was modified as expected when the form was submitted
             $this->assertEquals($expected, $model);
         }
 
@@ -88,7 +88,7 @@ The simplest ``TypeTestCase`` implementation looks like the following::
 So, what does it test? Here comes a detailed explanation.
 
 First you verify if the ``FormType`` compiles. This includes basic class
-inheritance, the ``buildForm()`` function and options resolution. This should
+inheritance, the ``buildForm()`` method and options resolution. This should
 be the first test you write::
 
     $form = $this->factory->create(TestedType::class, $formData);