From 621c7a2a73f5fbb22a3fd745a5a23a3b5446c3e8 Mon Sep 17 00:00:00 2001 From: Lars Dieckow Date: Mon, 27 May 2013 17:22:55 +0200 Subject: [PATCH] POD errors --- lib/Sipwise/CodingStandards.pm | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lib/Sipwise/CodingStandards.pm b/lib/Sipwise/CodingStandards.pm index d5dfc5c..1c045fc 100644 --- a/lib/Sipwise/CodingStandards.pm +++ b/lib/Sipwise/CodingStandards.pm @@ -18,7 +18,7 @@ This document describes Sipwise::CodingStandards version 1.002 This document outlines the coding standards for new Perl projects. Their purpose is to guide programmers to a common code style and practices, making decisions so you don't have to. Follow them unless you have a good reason not to. See -L for the rationale. Taking Perl's philosophy to heart, the +L for the rationale. Taking Perl's philosophy to heart, the standards are not enforced – it's up to the programmer to use common sense and sound judgement in applying them. The standards are not set in stone, either. If you notice that consistently I following them produces better @@ -55,8 +55,8 @@ distribution tarball name. However, using the module to handle versions, e.g. fo Do not use L. They are poorly understood. -Do not use underscores. Using underscores require to L the version to turn it into a number. If you want to mark -a distribution as release candidate to the PAUSE indexer, add the word C to the distribution name, see +Do not use underscores. Using underscores require to L the version to turn it into a number. If you want +to mark a distribution as release candidate to the PAUSE indexer, add the word C to the distribution name, see L. =head3 compliance