use "Form component" instead of "form framework"

Author: xabbuh

book/forms.rst

@@ -1867,7 +1867,7 @@ an array.
 
     Be advised, however, that in most cases using the ``getData()`` method is
     a better choice, since it returns the data (usually an object) after
-    it's been transformed by the form framework.
+    it's been transformed by the Form component.
 
 Adding Validation
 ~~~~~~~~~~~~~~~~~

book/translation.rst

@@ -573,7 +573,7 @@ the framework:
 Translating Constraint Messages
 -------------------------------
 
-If you're using validation constraints with the form framework, then translating
+If you're using validation constraints with the Form component, then translating
 the error messages is easy: simply create a translation resource for the
 ``validators`` :ref:`domain <using-message-domains>`.
 

cookbook/form/data_transformers.rst

@@ -169,8 +169,8 @@ when creating your form. Later, you'll learn how you could create a custom
 
 Cool, you're done! Your user will be able to enter an issue number into the
 text field and it will be transformed back into an Issue object. This means
-that, after a successful submission, the Form framework will pass a real Issue
-object to ``Task::setIssue()`` instead of the issue number.
+that, after a successful submission, the Form component will pass a real
+``Issue`` object to ``Task::setIssue()`` instead of the issue number.
 
 If the issue isn't found, a form error will be created for that field and
 its error message can be controlled with the ``invalid_message`` field option.