From fc9864eed3836d88d590f48783e6954eb1edaf75 Mon Sep 17 00:00:00 2001 From: Simon Welsh Date: Thu, 17 Apr 2014 17:44:54 +1200 Subject: [PATCH] Wording fix to forms.md Closes #3032 --- docs/en/topics/forms.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/en/topics/forms.md b/docs/en/topics/forms.md index 41eeff251..e05c9fedb 100644 --- a/docs/en/topics/forms.md +++ b/docs/en/topics/forms.md @@ -9,11 +9,11 @@ form. A fully implemented form in SilverStripe includes a couple of classes that individually have separate concerns. -* Controller—Takes care of assembling the form and receiving data from it. -* Form—Holds sets of fields, actions and validators. -* FormField —Fields that receive data or displays them, e.g input fields. -* FormActions—Often submit buttons that executes actions. -* Validators—Validate the whole form. +* Controller — Takes care of assembling the form and receiving data from it. +* Form — Holds sets of fields, actions and validators. +* FormField — Fields that receive data or displays them, e.g input fields. +* FormActions — Buttons that execute actions. +* Validators — Validate the whole form. Depending on your needs you can customize and override any of the above classes; the defaults, however, are often sufficient.