[DOCS] Fix minor typos in form documentation

Some typos are fixed. Additionally the spelling of "customise" was
adjusted to en-us.

Resolves: #89674
Releases: master, 9.5
Change-Id: I982c8438405677b6435e38cad5f7dbb6a6e886f7
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62324
Tested-by: TYPO3com <noreply@typo3.com>
Tested-by: Daniel Goerz <daniel.goerz@posteo.de>
Reviewed-by: Daniel Siepmann <coding@daniel-siepmann.de>
Reviewed-by: Daniel Goerz <daniel.goerz@posteo.de>

typo3/sysext/form/Documentation/Concepts/Configuration/Index.rst

@@ -60,7 +60,7 @@ module.
 .. hint::
 
    We recommend using a `site package <https://de.slideshare.net/benjaminkott/typo3-the-anatomy-of-sitepackages>`_.
-   This will make your life easier if you want to customise EXT:form
+   This will make your life easier if you want to customize EXT:form
    heavily in order to suit the customer's needs.
 
 

typo3/sysext/form/Documentation/Concepts/Finishers/Index.rst

@@ -207,7 +207,7 @@ submitted form values (assuming you are using the ``parseOption()`` method).
 You can access values of the ``FormRuntime`` and thus values of each single
 form element by encapsulating the option values with ``{}``. If there is a
 form element with the ``identifier`` 'subject', you can access its value
-within the the finisher configuration. Check out the following example to
+within the finisher configuration. Check out the following example to
 get the whole idea.
 
 .. code-block:: yaml

typo3/sysext/form/Documentation/Config/proto/finishersDefinition/finishers/SaveToDatabase.rst

@@ -351,8 +351,8 @@ options.databaseColumnMappings.<databaseColumnName>.value
       You can also use the :ref:`FormRuntime accessor feature<concepts-finishers-customfinisherimplementations-accessingoptions-formruntimeaccessor>` to access every getable property from the ``FormRuntime``
       In short: use something like ``{<formElementIdentifier>}`` to get the value from the submitted form element with the identifier ``<formElementIdentifier>``.
 
-      If you use the FormRuntime accessor feature within ``options.databaseColumnMappings``, than the functionality is nearly equal
-      to the the ``options.elements`` configuration variant.
+      If you use the FormRuntime accessor feature within ``options.databaseColumnMappings`` the functionality is nearly equal
+      to the ``options.elements`` configuration variant.
 
 
 .. _typo3.cms.form.prototypes.<prototypeIdentifier>.finishersdefinition.savetodatabase.options.databasecolumnmappings.<databasecolumnname>.skipifvalueisempty:

typo3/sysext/form/Documentation/Config/proto/formElements/formEditor/inspectorEditors/PropertyGridEditor.rst

@@ -80,7 +80,7 @@ isSortable
       - :ref:`"Inspector"<concepts-formeditor-inspector>`
 
 :aspect:`Description`
-      If set to 'false' then the rows are not sortable.
+      If set to 'false' the rows are not sortable.
 
 
 .. _typo3.cms.form.prototypes.<prototypeidentifier>.formelementsdefinition.<formelementtypeidentifier>.formeditor.editors.*.enableaddrow-propertygrideditor:
@@ -104,7 +104,7 @@ enableAddRow
       - :ref:`"Inspector"<concepts-formeditor-inspector>`
 
 :aspect:`Description`
-      If set to 'false' the the "add new row" button is disabled.
+      If set to 'false' the "add new row" button is disabled.
 
 
 .. _typo3.cms.form.prototypes.<prototypeidentifier>.formelementsdefinition.<formelementtypeidentifier>.formeditor.editors.*.enabledeleterow-propertygrideditor:
@@ -128,7 +128,7 @@ enableDeleteRow
       - :ref:`"Inspector"<concepts-formeditor-inspector>`
 
 :aspect:`Description`
-      If set to 'false' the the "delete row" button is disabled.
+      If set to 'false' the "delete row" button is disabled.
 
 
 .. _typo3.cms.form.prototypes.<prototypeidentifier>.formelementsdefinition.<formelementtypeidentifier>.formeditor.editors.*.multiselection-propertygrideditor:
@@ -152,7 +152,7 @@ multiSelection
       - :ref:`"Inspector"<concepts-formeditor-inspector>`
 
 :aspect:`Description`
-      If set to 'false' then only one row can be marked as preselected.
+      If set to 'false' only one row can be marked as preselected.
 
 
 .. _typo3.cms.form.prototypes.<prototypeidentifier>.formelementsdefinition.<formelementtypeidentifier>.formeditor.editors.*.removelastavailablerowflashmessagetitle-propertygrideditor:
@@ -177,7 +177,7 @@ removeLastAvailableRowFlashMessageTitle
       - :ref:`"Translate form editor settings"<concepts-formeditor-translation-formeditor>`
 
 :aspect:`Description`
-      There must be at least one existing row within this ``inspector editor``. If the last existing row is tried to be removed then a flash message is shown.
+      There must be at least one existing row within this ``inspector editor``. If the last existing row is tried to be removed a flash message is shown.
       This property define the title for the flash message.
 
 
@@ -203,7 +203,7 @@ removeLastAvailableRowFlashMessageMessage
       - :ref:`"Translate form editor settings"<concepts-formeditor-translation-formeditor>`
 
 :aspect:`Description`
-      There must be at least one existing row within this ``inspector editor``. If the last existing row is tried to be removed then a flash message is shown.
+      There must be at least one existing row within this ``inspector editor``. If the last existing row is tried to be removed a flash message is shown.
       This property define the text for the flash message.
 
 
@@ -229,4 +229,4 @@ shouldShowPreselectedValueColumn
       - :ref:`"Inspector"<concepts-formeditor-inspector>`
 
 :aspect:`Description`
-      If set to 'false' then the column which is used to mark a row as preselected will be disabled.
+      If set to 'false' the column which is used to mark a row as preselected will be disabled.

typo3/sysext/form/Documentation/Introduction/Index.rst

@@ -55,7 +55,7 @@ Features List
 The following list names some features of the form framework:
 
 * form editor
-   * fully customisable editor for building complex forms
+   * fully customizable editor for building complex forms
    * replaceable and extendible form editor components
    * JS API to extend form editor
 * PHP API