Update of /cvsroot/module-build/Module-Build/lib/Module/Build
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16771/lib/Module/Build
Modified Files:
Authoring.pod
Log Message:
Minor doc fixes.
Index: Authoring.pod
===================================================================
RCS file: /cvsroot/module-build/Module-Build/lib/Module/Build/Authoring.pod,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -d -r1.25 -r1.26
--- Authoring.pod 29 Nov 2005 05:18:40 -0000 1.25
+++ Authoring.pod 30 Nov 2005 10:46:04 -0000 1.26
@@ -352,7 +352,7 @@
You can combine references to your own variables or subroutines with
unreferenced specifications, for which the result will also be stored in the
-has returned by C<args()>. For example:
+hash returned by C<args()>. For example:
my $loud = 0;
my $build = Module::Build->new(
@@ -1170,7 +1170,7 @@
Returns a human-readable (table-form) string showing all
prerequisites, the versions required, and the versions actually
-installed. This can be useful for reviewing the configuration of your
+installed. This can be useful for reviewing the configuration of your
system prior to a build, or when compiling data to send for a bug
report. The C<prereq_report> action is just a thin wrapper around the
C<prereq_report()> method.
@@ -1266,9 +1266,9 @@
cause problems with the distribution.
Each of the three types of prerequisites listed above can be applied
-to different aspects of the Build process. For the module distribution
-itself you simply define "requires", "recommends", or "conflicts". The
-types can also apply to other aspects of the Build process. Currently,
+to different aspects of the Build process. For the module distribution
+itself you simply define "requires", "recommends", or "conflicts". The
+types can also apply to other aspects of the Build process. Currently,
only "build_requires" is defined which is used for modules which are
required during the Build process.
|
