From 893e9785f34b33b1376654f1631f44f75453fbc4 Mon Sep 17 00:00:00 2001 From: Bruno Baguette <1922257+Levure@users.noreply.github.com> Date: Wed, 10 Jun 2020 18:59:36 +0200 Subject: [PATCH] =?UTF-8?q?Added=20missing=20space=20:=20everytime=20?= =?UTF-8?q?=E2=AE=9E=20every=20time?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- form/create_custom_field_type.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/form/create_custom_field_type.rst b/form/create_custom_field_type.rst index 5698462487e..571b4003fa9 100644 --- a/form/create_custom_field_type.rst +++ b/form/create_custom_field_type.rst @@ -19,7 +19,7 @@ be implemented with a :doc:`ChoiceType ` where th ``choices`` option is set to the list of available shipping options. However, if you use the same form type in several forms, repeating the list of -``choices`` everytime you use it quickly becomes boring. In this example, a +``choices`` every time you use it quickly becomes boring. In this example, a better solution is to create a custom form type based on ``ChoiceType``. The custom type looks and behaves like a ``ChoiceType`` but the list of choices is already populated with the shipping options so you don't need to define them.