Fix some typos and formatting in the Bugzilla::Extension POD.

git-svn-id: svn://10.0.0.236/trunk@259902 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
mkanat%bugzilla.org 2010-03-08 01:33:57 +00:00
parent 16d2e33c1b
commit db8c7b06d7
4 changed files with 9 additions and 9 deletions

View File

@ -1 +1 @@
7052 7053

View File

@ -381,7 +381,7 @@ described in the L</Where Extension Code Goes> section above.
During your subroutine, you may want to know what values were passed During your subroutine, you may want to know what values were passed
as CGI arguments to the current script, or what arguments were passed to as CGI arguments to the current script, or what arguments were passed to
the current WebService method. You can get that data via the current WebService method. You can get that data via
<Bugzilla/input_params>. L<Bugzilla/input_params>.
=head3 Adding New Hooks To Bugzilla =head3 Adding New Hooks To Bugzilla
@ -447,8 +447,8 @@ named C<Foo>:
Note that it is I<not> a subclass of C<Bugzilla::Extension>, because Note that it is I<not> a subclass of C<Bugzilla::Extension>, because
at the time that module requirements are being checked in L<checksetup>, at the time that module requirements are being checked in L<checksetup>,
C<Bugzilla::Extension> cannot be loaded. Also, just like F<Extension.pm>, C<Bugzilla::Extension> cannot be loaded. Also, just like F<Extension.pm>,
it ends with C<< __PACKAGE__->NAME; >>. Note also that it has the exact it ends with C<< __PACKAGE__->NAME; >>. Note also that it has the
same C<package> name as F<Extension.pm>. B<exact same> C<package> name as F<Extension.pm>.
This file may not use any Perl modules other than L<Bugzilla::Constants>, This file may not use any Perl modules other than L<Bugzilla::Constants>,
L<Bugzilla::Install::Util>, L<Bugzilla::Install::Requirements>, and L<Bugzilla::Install::Util>, L<Bugzilla::Install::Requirements>, and
@ -483,8 +483,8 @@ which should have C<package Bugzilla::Extension::Foo::Bar;> as its package
name. name.
This allows any place in Bugzilla to load your modules, which is important This allows any place in Bugzilla to load your modules, which is important
for some hooks. It even allows other extensions to load your modules. It for some hooks. It even allows other extensions to load your modules, and
even allows you to install your modules into the global Perl install allows you to install your modules into the global Perl install
as F<Bugzilla/Extension/Foo/Bar.pm>, if you'd like, which helps allow CPAN as F<Bugzilla/Extension/Foo/Bar.pm>, if you'd like, which helps allow CPAN
distribution of Bugzilla extensions. distribution of Bugzilla extensions.
@ -594,7 +594,7 @@ C<header>.
This is the name of the hook--what you saw in C<Hook.process> inside This is the name of the hook--what you saw in C<Hook.process> inside
of the template you want to hook. In our example, this is of the template you want to hook. In our example, this is
C<additioanl_header>. C<additional_header>.
=item <template type> =item <template type>

View File

@ -1,6 +1,6 @@
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [ <!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" [
<!ENTITY conventions SYSTEM "conventions.xml"> ] > --> <!ENTITY conventions SYSTEM "conventions.xml"> ] > -->
<!-- $Id: about.xml,v 1.27 2010-03-08 01:16:25 mkanat%bugzilla.org Exp $ --> <!-- $Id: about.xml,v 1.28 2010-03-08 01:31:33 mkanat%bugzilla.org Exp $ -->
<chapter id="about"> <chapter id="about">
<title>About This Guide</title> <title>About This Guide</title>

View File

@ -1,5 +1,5 @@
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> --> <!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> -->
<!-- $Id: installation.xml,v 1.177 2010-03-08 01:16:25 mkanat%bugzilla.org Exp $ --> <!-- $Id: installation.xml,v 1.178 2010-03-08 01:31:33 mkanat%bugzilla.org Exp $ -->
<chapter id="installing-bugzilla"> <chapter id="installing-bugzilla">
<title>Installing Bugzilla</title> <title>Installing Bugzilla</title>