Bug #126944 for BIND-Conf_Parser: Spelling errors

Hello, some little errors

Description: Spelling error patch Author: Axel Beckert <abe@debian.org> Forwarded: no Reviewed-By: Xavier Guimard <x.guimard@free.fr> Last-Update: 2018-08-25 Index: libbind-confparser-perl/lib/BIND/Conf_Parser.pm =================================================================== --- libbind-confparser-perl.orig/lib/BIND/Conf_Parser.pm 2014-01-01 07:47:29.748931491 +0100 +++ libbind-confparser-perl/lib/BIND/Conf_Parser.pm 2014-01-01 07:47:44.289008410 +0100 @@ -1048,7 +1048,7 @@ C<BIND::Conf_Parser> does not perform all the syntactic checks performed by the parser in F<named> itself. For example, port numbers -are not verified to be positive intergers in the range 0 to 65535. +are not verified to be positive integers in the range 0 to 65535. The parse() method cannot be called multiple times with parts of statements. @@ -1058,7 +1058,7 @@ Some callbacks are invoked before the semicolon that terminates the corresponding syntactic form is actually recognized. It is therefore possible for a syntax error to not be detected until after a callback -is invoked for the presumably completly parsed form. No attempt is +is invoked for the presumably completely parsed form. No attempt is made to delay the invocation of callbacks to the completion of toplevel statements. @@ -1074,7 +1074,7 @@ A C<BIND::Conf_Parser> object is a blessed anonymous hash. In an attempt to prevent modules trampling on each other I propose that any -subclass that requires persistant state between calls to the callback +subclass that requires persistent state between calls to the callback routines (handle_foo()) and other subclass methods should prefix its keys names with its own name separated by _'s. For example, a hypothetical C<BIND::Conf_Parser::Keys> module would keep data under