[Catalyst-commits] r12250 - trunk/examples/CatalystAdvent/root/2009

[caelum at dev.catalyst.perl.org]

Author: caelum
Date: 2009-12-08 01:20:15 +0000 (Tue, 08 Dec 2009)
New Revision: 12250

Modified:
   trunk/examples/CatalystAdvent/root/2009/8.pod
Log:
add periods to numbers for list

Modified: trunk/examples/CatalystAdvent/root/2009/8.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2009/8.pod	2009-12-08 01:08:51 UTC (rev 12249)
+++ trunk/examples/CatalystAdvent/root/2009/8.pod	2009-12-08 01:20:15 UTC (rev 12250)
@@ -21,12 +21,12 @@
 
 =over
 
-=item 1
+=item 1.
 
 Unattended installation: the majority of our packages require absolutely no
 user interaction during installation, in contrast to installs via CPAN. 
 
-=item 2
+=item 2.
 
 Quicker installs for binary packages: since binary packages are pre-built,
 installing the package is as simple as unpacking the package and installing
@@ -34,7 +34,7 @@
 (as with Catalyst and MojoMojo), this can result in a significant time
 savings, especially when one considers rebuilding due to upgrades. 
 
-=item 3
+=item 3.
 
 No unnecessary updates: if an update only affects the Win32 platform, for
 example, it does not make sense to waste bandwidth downloading and installing
@@ -42,7 +42,7 @@
 those that have no functional difference to users, saving time, bandwidth,
 and administrative overhead.
 
-=item 4
+=item 4.
 
 Only packages offered by Debian are supported by Debian: if there are bugs
 in your Debian software, it is our responsibility to help identify and
@@ -50,7 +50,7 @@
 developers (i.e. the Catalyst community) and working toward a solution
 together - but our team takes care of this on your behalf.
 
-=item 5
+=item 5.
 
 Updates occur with the rest of your system: while upgrading your system
 using aptitude, synaptic, or another package management tool, your Perl
@@ -58,7 +58,7 @@
 administrator forgets to update CPAN packages periodically, leaving your
 systems vulnerable to potential security issues.
 
-=item 6
+=item 6.
 
 Important changes are always indicated during package upgrades: if there are
 changes to the API of a library which can potentially break applications, a