Typos in Doku

diff --git a/SL/Controller/Helper/ParseFilter.pm b/SL/Controller/Helper/ParseFilter.pm
index 37b06737d1935fe8b13d9a8e2a703089ab1c1ceb..491eb63b58b9a6682b13b6b2f9280c892ed5f712 100644 (file)
--- a/SL/Controller/Helper/ParseFilter.pm
+++ b/SL/Controller/Helper/ParseFilter.pm
@@ -257,7 +257,7 @@ SL::Controller::Helper::ParseFilter - Convert a form filter spec into a RDBO get
 
 A search filter will usually search for things in relations of the actual
 search target. A search for sales orders may be filtered by the name of the
 
 A search filter will usually search for things in relations of the actual
 search target. A search for sales orders may be filtered by the name of the

-customer. L<Rose::DB::Object> alloes you to search for these by filtering them prefixed with their table:
+customer. L<Rose::DB::Object> allows you to search for these by filtering them prefixed with their table:

 
   query => [
     'customer.name'          => 'John Doe',
 
   query => [
     'customer.name'          => 'John Doe',


@@ -265,7 +265,7 @@ customer. L<Rose::DB::Object> alloes you to search for these by filtering them p
     'orddate'                => [ lt    => DateTime->today ],
   ]
 
     'orddate'                => [ lt    => DateTime->today ],
   ]
 

-Unfortunately, if you specify them in you form as these strings, the form
+Unfortunately, if you specify them in your form as these strings, the form

 parser will convert them into nested structures like this:
 
   $::form = bless {
 parser will convert them into nested structures like this:
 
   $::form = bless {


@@ -297,7 +297,7 @@ specific L<Salesman>:
 
   [% L.select_tag('filter.salesman.id', ...) %]
 
 
   [% L.select_tag('filter.salesman.id', ...) %]
 

-Additionally you can add modifier to the name to set a certain method:
+Additionally you can add a modifier to the name to set a certain method:

 
   [% L.input_tag('filter.department.description:substr::ilike', ...) %]
 
 
   [% L.input_tag('filter.department.description:substr::ilike', ...) %]
 


@@ -313,7 +313,7 @@ list of modifiers.
 =head1 LAUNDERING
 
 Unfortunately Template cannot parse the postfixes if you want to
 =head1 LAUNDERING
 
 Unfortunately Template cannot parse the postfixes if you want to

-rerender the filter. For this reason all colons filter keys are by
+rerender the filter. For this reason all colon filter keys are by

 default laundered into underscores, so you can use them like this:
 
   [% L.input_tag('filter.price:number::lt', filter.price_number__lt) %]
 default laundered into underscores, so you can use them like this:
 
   [% L.input_tag('filter.price:number::lt', filter.price_number__lt) %]


@@ -326,7 +326,7 @@ these will get copied into a _ suffixed version as hashes:
 All of your original entries will stay intact. If you don't want this to
 happen pass C<< no_launder => 1 >> as a parameter.  Additionally you can pass a
 different target for the laundered values with the C<launder_to>  parameter. It
 All of your original entries will stay intact. If you don't want this to
 happen pass C<< no_launder => 1 >> as a parameter.  Additionally you can pass a
 different target for the laundered values with the C<launder_to>  parameter. It

-takes an hashref and will deep copy all values in your filter to the target. So
+takes a hashref and will deep copy all values in your filter to the target. So

 if you have a filter that looks like this:
 
   $filter = {
 if you have a filter that looks like this:
 
   $filter = {


@@ -382,7 +382,7 @@ will expand to:
     ]
   ]
 
     ]
   ]
 

-For more abuot custom filters, see L<SL::DB::Helper::Filtered>.
+For more about custom filters, see L<SL::DB::Helper::Filtered>.

 
 =head1 FILTERS (leading with :)
 
 
 =head1 FILTERS (leading with :)
 


@@ -450,7 +450,7 @@ following will not work as you expect:
   L.input_tag('customer.name:substr::ilike', ...)
   L.input_tag('invoice.customer.name:substr::ilike', ...)
 
   L.input_tag('customer.name:substr::ilike', ...)
   L.input_tag('invoice.customer.name:substr::ilike', ...)
 

-This will sarch for orders whose invoice has the _same_ customer, which matches
+This will search for orders whose invoice has the _same_ customer, which matches

 both inputs. This is because tables are aliased by their name and not by their
 position in with_objects.
 
 both inputs. This is because tables are aliased by their name and not by their
 position in with_objects.
 


@@ -460,7 +460,7 @@ position in with_objects.
 
 =item *
 
 
 =item *
 

-Additional filters shoud be pluggable.
+Additional filters should be pluggable.

 
 =back
 
 
 =back
 

diff --git a/SL/DBUtils.pm b/SL/DBUtils.pm
index 689340ac2299224b8e6ec2c6ec14fff0c5f78e42..8e1ad458a0abb214773c93cb4426c64558b0111d 100644 (file)
--- a/SL/DBUtils.pm
+++ b/SL/DBUtils.pm
@@ -389,7 +389,7 @@ __END__
 
 =head1 NAME
 
 
 =head1 NAME
 

-SL::DBUTils.pm: All about Databaseconections in Lx
+SL::DBUTils.pm: All about database connections in kivitendo

 
 =head1 SYNOPSIS
 
 
 =head1 SYNOPSIS
 


@@ -422,7 +422,7 @@ Using DBUtils most database procedures can be reduced to defining the query, exe
 
 DBUtils relies heavily on two parameters which have to be passed to almost every function: $form and $dbh.
   - $form is used for error handling only. It can be omitted in theory, but should not.
 
 DBUtils relies heavily on two parameters which have to be passed to almost every function: $form and $dbh.
   - $form is used for error handling only. It can be omitted in theory, but should not.

-  - $dbh is a handle to the databe, as returned by the DBI::connect routine. If you don't have an active connectiong, you can query $form->get_standard_dbh() to get a generic no_auto connection. Don't forget to commit in this case!
+  - $dbh is a handle to the database, as returned by the DBI::connect routine. If you don't have an active connection, you can query $form->get_standard_dbh() to get a generic no_auto connection. Don't forget to commit in this case!

 
 
 Every function here should accomplish the follwing things:
 
 
 Every function here should accomplish the follwing things:

diff --git a/SL/Helper/Csv.pm b/SL/Helper/Csv.pm
index 88e61cb63a94723e1236c54935ef8c733af03fae..43aaabb911764c1988e548d33919a1b74e5986b9 100644 (file)
--- a/SL/Helper/Csv.pm
+++ b/SL/Helper/Csv.pm
@@ -119,7 +119,7 @@ sub _check_multiplexed {
         0,
         0]) unless $info_ok;
 
         0,
         0]) unless $info_ok;
 

-      # If header is given, there need to be a header for each profile
+      # If header is given, there needs to be a header for each profile

       # and no empty headers.
       if ($info_ok && $self->header) {
         my @header = @{ $self->header };
       # and no empty headers.
       if ($info_ok && $self->header) {
         my @header = @{ $self->header };


@@ -195,7 +195,7 @@ sub _check_header {
   # people insist that case sensitivity doesn't exist and try to enter all
   # sorts of stuff. at this point we've got a profile (with keys that represent
   # valid methods), and a header full of strings. if two of them match, the user
   # people insist that case sensitivity doesn't exist and try to enter all
   # sorts of stuff. at this point we've got a profile (with keys that represent
   # valid methods), and a header full of strings. if two of them match, the user

-  # mopst likely meant that field, so rewrite the header
+  # most likely meant that field, so rewrite the header

   if ($self->case_insensitive_header) {
     die 'case_insensitive_header is only possible with profile' unless $self->profile;
     if ($header) {
   if ($self->case_insensitive_header) {
     die 'case_insensitive_header is only possible with profile' unless $self->profile;
     if ($header) {


@@ -221,7 +221,7 @@ sub _check_header {
 sub _check_multiplex_datatype_position {
   my ($self) = @_;
 
 sub _check_multiplex_datatype_position {
   my ($self) = @_;
 

-  return 1 if !$self->is_multiplexed; # ok if if not multiplexed
+  return 1 if !$self->is_multiplexed; # ok if not multiplexed

 
   my @positions = map { firstidx { 'datatype' eq lc($_) } @{ $_ } } @{ $self->header };
   my $first_pos = $positions[0];
 
   my @positions = map { firstidx { 'datatype' eq lc($_) } @{ $_ } } @{ $self->header };
   my $first_pos = $positions[0];


@@ -368,8 +368,8 @@ SL::Helper::Csv - take care of csv file uploads
 
 See Synopsis.
 
 
 See Synopsis.
 

-Text::CSV offeres already good functions to get lines out of a csv file, but in
-most cases you will want those line to be parsed into hashes or even objects,
+Text::CSV already offers good functions to get lines out of a csv file, but in
+most cases you will want those lines to be parsed into hashes or even objects,

 so this model just skips ahead and gives you objects.
 
 Its basic assumptions are:
 so this model just skips ahead and gives you objects.
 
 Its basic assumptions are:


@@ -378,7 +378,7 @@ Its basic assumptions are:
 
 =item You do know what you expect to be in that csv file.
 
 
 =item You do know what you expect to be in that csv file.
 

-This means first and foremost you have knowledge about encoding, number and
+This means first and foremost that you have knowledge about encoding, number and

 date format, csv parameters such as quoting and separation characters. You also
 know what content will be in that csv and what L<Rose::DB> is responsible for
 it. You provide valid header columns and their mapping to the objects.
 date format, csv parameters such as quoting and separation characters. You also
 know what content will be in that csv and what L<Rose::DB> is responsible for
 it. You provide valid header columns and their mapping to the objects.


@@ -493,8 +493,8 @@ accessors. Example:
 In this case C<listprice_as_number> will be used to read in values from the
 C<listprice> column.
 
 In this case C<listprice_as_number> will be used to read in values from the
 C<listprice> column.
 

-In case of a One-To-One relationsship these can also be set over
-relationsships by sparating the steps with a dot (C<.>). This will work:
+In case of a One-To-One relationship these can also be set over
+relationships by separating the steps with a dot (C<.>). This will work:

 
   [ {profile => { customer => 'customer.name' }} ]
 
 
   [ {profile => { customer => 'customer.name' }} ]