From 677dc9822e35933a9fe03ce0d57837417a7badc5 Mon Sep 17 00:00:00 2001 From: Fred Condo Date: Wed, 8 May 2013 17:00:43 -0700 Subject: [PATCH] Edit forms documentation Correct spelling and word choices. --- docs/en/topics/forms.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/en/topics/forms.md b/docs/en/topics/forms.md index 5ac3189f3..ee4c27fc6 100644 --- a/docs/en/topics/forms.md +++ b/docs/en/topics/forms.md @@ -7,18 +7,18 @@ and handle the actions and data from a form. A fully implemented form in SilverStripe includes a couple of classes that individually have separate concerns. - * Controller - Takes care of assemble the form and recieving data from it. + * Controller - Takes care of assembling the form and receiving data from it. * Form - Holds sets of fields, actions and validators. - * FormField - Fields that recieves data or displays them, e.g input fields. + * FormField - Fields that receive data or displays them, e.g input fields. * FormActions - Often submit buttons that executes actions. - * Validators - Validates the whole form, see [Form validation](form-validation.md) topic for more information. + * Validators - Validate the whole form, see [Form validation](form-validation.md) topic for more information. Depending on your needs you can customize and override any of the above classes, however the defaults are often sufficient. ## The Controller -Forms start at the controller. Here is an simple example on how to set up a form in a controller. +Forms start at the controller. Here is a simple example on how to set up a form in a controller. **Page.php**