Merge pull request #53 from dsteinbrunner/patch-1

typo fixes

lib/HTML/FormHandler.pm

@@ -1374,7 +1374,7 @@ sub setup_form {
             $self->_result_from_object( $self->result, $init_object );
         }
         elsif ( !$self->posted ) {
-            # no initial object. empty form form must be initialized
+            # no initial object. empty form must be initialized
             $self->_result_from_fields( $self->result );
         }
     }

lib/HTML/FormHandler/BuildFields.pm

@@ -292,7 +292,7 @@ sub _merge_updates {
             $all_updates = merge( $all_updates, { tags => $self->form->widget_tags } );
         }
     }
-    # get updates from compund field update_subfields and widget_tags
+    # get updates from compound field update_subfields and widget_tags
     if ( $self->has_flag('is_compound') ) {
         my $comp_field_updates = $self->update_subfields;
         my $comp_all_updates = {};

lib/HTML/FormHandler/Field/Captcha.pm

@@ -8,7 +8,7 @@ use HTTP::Date;
 =head1 SYNOPSIS
 
 A Captcha class using GD::SecurityImage.
-Requires that that three methods be available from a form object:
+Requires that three methods be available from a form object:
 
   $self->form->get_captcha;
   $self->form->set_captcha;

lib/HTML/FormHandler/Field/Date.pm

@@ -93,7 +93,7 @@ sub get_class_messages  {
 sub date_deflate {
     my ( $self, $value ) = @_;
 
-    # if not a DateTime, assume correctly formated string and return
+    # if not a DateTime, assume correctly formatted string and return
     return $value unless ref $value eq 'DateTime';
     my $format = $self->get_strf_format;
     my $string = $value->strftime($format);

lib/HTML/FormHandler/Field/Email.pm

@@ -49,7 +49,7 @@ apply(
 
 =head1 DESCRIPTION
 
-Validates that the input looks like an email address uisng L<Email::Valid>.
+Validates that the input looks like an email address using L<Email::Valid>.
 Widget type is 'text'.
 
 If form has 'is_html5' flag active it will render <input type="email" ... />

lib/HTML/FormHandler/Field/Money.pm

@@ -48,7 +48,7 @@ apply(
 
 =head1 DESCRIPTION
 
-Validates that a postive or negative real value is entered.
+Validates that a positive or negative real value is entered.
 Formatted with two decimal places.
 
 Uses a period for the decimal point. Widget type is 'text'.

lib/HTML/FormHandler/Field/Repeatable.pm

@@ -52,7 +52,7 @@ This class represents an array. It can either be an array of hashrefs
 The 'contains' keyword is used for elements that do not have names
 because they are not hash elements.
 
-This field node will build arrays of fields from the the parameters or an
+This field node will build arrays of fields from the parameters or an
 initial object, or empty fields for an empty form.
 
 The name of the element fields will be an array index,

lib/HTML/FormHandler/Field/Select.pm

@@ -136,7 +136,7 @@ Setting the select element to disabled:
       return @selections;
    }
 
-You can also devide the options up into option groups. See the section on
+You can also divide the options up into option groups. See the section on
 rendering.
 
 =head2 Reloading options

lib/HTML/FormHandler/Fields.pm

@@ -17,7 +17,7 @@ num_fields, has_fields, and set_field_at methods.
 
 =head2 field( $full_name )
 
-Return the field objct with the full_name passed. Will return undef
+Return the field object with the full_name passed. Will return undef
 if the field is not found, or will die if passed a second parameter.
 
 =head2 field_index

lib/HTML/FormHandler/Manual/FromDFV.pod

@@ -16,7 +16,7 @@ to add, patches are welcome.
 In a general way, FormHandler doesn't have nearly so many "special"
 checks as Data::FormValidator. It would be possible to implement many
 of them, but there hasn't been much demand for them. So far FormHandler
-users seem to be satisfed with the "do your own checks in a Perl method"
+users seem to be satisfied with the "do your own checks in a Perl method"
 solution. Because of the greater complexity of FormHandler's data model -
 with Repeatable arrays and nested compounds, etc - it's somewhat harder
 to do some of them automatically.
@@ -72,7 +72,7 @@ directly in a FormHandler form:
 
 =item email
 
-Use the 'Email' field type, or use the the FH Moose Type, 'email'.
+Use the 'Email' field type, or use the FH Moose Type, 'email'.
 
      has_field 'email' => ( type => 'Email' );
      -- or --

lib/HTML/FormHandler/Manual/FromFF.pod

@@ -133,7 +133,7 @@ things in the form's 'validate' sub.
 
 =item Email
 
-Use the 'Email' field type, or use the the FH Moose Type, 'email'.
+Use the 'Email' field type, or use the FH Moose Type, 'email'.
 
      has_field 'email' => ( type => 'Email' );
      -- or --

lib/HTML/FormHandler/Manual/Intro.pod

@@ -142,7 +142,7 @@ template.
 The form object will give you a hashref of values suitable for
 filling in the form with C<< $form->fif >>.
 
-By default FormHandler structures fields (and renders thems) in a way
+By default FormHandler structures fields (and renders them) in a way
 that matches the database. If you want to organize the rendering output
 in different ways, you can use blocks to organize your fields.
 

lib/HTML/FormHandler/Manual/Rendering.pod

@@ -510,7 +510,7 @@ The 'first_fset' block will render like this:
     </fieldset>
 
 In order to actually get this block to be used when you render with
-C<< $form->render >>, you need to supply a 'render_list' on the the form
+C<< $form->render >>, you need to supply a 'render_list' on the form
 level:
 
    sub build_render_list { ['first_fset', 'submit_btn'] }

lib/HTML/FormHandler/Model/CDBI.pm

@@ -149,7 +149,7 @@ The active column name is determined by calling:
         : $field->active_column;
 
 Which allows setting the name of the active column globally if
-your tables are consistantly named (all lookup tables have the same
+your tables are consistently named (all lookup tables have the same
 column name to indicate they are active), or on a per-field basis.
 
 In addition, if the foreign class is the same as the item's class (or the class returned

lib/HTML/FormHandler/Render/Simple.pm

@@ -105,7 +105,7 @@ Output an HTML string for a 'checkbox' widget
 
 Output an HTML string for a 'radio_group' selection widget.
 This widget should be for a field that inherits from 'Select',
-since it requires the existance of an 'options' array.
+since it requires the existence of an 'options' array.
 
 =head2 render_textarea