[Module-build-checkins] Module-Build/website META-spec.pod,1.10,1.11

[Ken W. <kwi...@us...>]

Update of /cvsroot/module-build/Module-Build/website
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv27887

Modified Files:
	META-spec.pod 
Log Message:
Fix formatting

Index: META-spec.pod
===================================================================
RCS file: /cvsroot/module-build/Module-Build/website/META-spec.pod,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11
--- META-spec.pod	24 Oct 2005 03:31:56 -0000	1.10
+++ META-spec.pod	24 Oct 2005 03:35:10 -0000	1.11
@@ -111,13 +111,13 @@
 
 Some fields require a version specification (ex. L<"requires">,
 L<"recommends">, L<"build_requires">, etc.) to indicate the particular
-version(s) of some other module that may be required as a
+versionZ<>(s) of some other module that may be required as a
 prerequisite.  This section details the version specification formats
 that are currently supported.
 
 The simplest format for a version specification is just the version
-number itself, e.g. C<2.4>.  This means that C<at least> version 2.4
-must be present.  To indicate that C<any> version of a prerequisite is
+number itself, e.g. C<2.4>.  This means that B<at least> version 2.4
+must be present.  To indicate that B<any> version of a prerequisite is
 okay, even if the prerequisite doesn't define a version at all, use
 the version C<0>.