pkglint*: Start sentence with a capital letter

From Thomas Orgis in private mail.

4 files changed, 8 insertions, 8 deletions

diff --git a/pkgtools/pkglint/files/pkglint.go b/pkgtools/pkglint/files/pkglint.go
index 5d9e0fb8f3e..d9329d46f43 100644
--- a/pkgtools/pkglint/files/pkglint.go
+++ b/pkgtools/pkglint/files/pkglint.go
@@ -163,7 +163,7 @@ func (pkglint *Pkglint) PrintSummary() {
 				G.errors, ifelseStr(G.errors == 1, "error", "errors"),
 				G.warnings, ifelseStr(G.warnings == 1, "warning", "warnings"))
 		} else {
-			io.WriteString(G.logOut, "looks fine.\n")
+			io.WriteString(G.logOut, "Looks fine.\n")
 		}
 		if G.explanationsAvailable && !G.opts.Explain {
 			fmt.Fprint(G.logOut, "(Run \"pkglint -e\" to show explanations.)\n")
diff --git a/pkgtools/pkglint4/files/PkgLint/Logging.pm b/pkgtools/pkglint4/files/PkgLint/Logging.pm
index eecb17a6a59..544ab118f4d 100644
--- a/pkgtools/pkglint4/files/PkgLint/Logging.pm
+++ b/pkgtools/pkglint4/files/PkgLint/Logging.pm
@@ -1,4 +1,4 @@
-# $NetBSD: Logging.pm,v 1.1 2015/11/25 16:42:21 rillig Exp $
+# $NetBSD: Logging.pm,v 1.2 2017/10/02 14:41:21 wiz Exp $
 #
 # Subroutines for printing messages to the user in a common format.
 # The subroutines all have the parameters C<$fname>,
@@ -122,7 +122,7 @@ sub print_summary_and_exit($) {
 		if ($errors != 0 || $warnings != 0) {
 			print("$errors errors and $warnings warnings found." . ($explain_flag ? "" : " (Use -e for more details.)") . "\n");
 		} else {
-			print "looks fine.\n";
+			print "Looks fine.\n";
 		}
 	}
 	exit($errors != 0);
diff --git a/pkgtools/pkglint4/files/doc/chap.design.xml b/pkgtools/pkglint4/files/doc/chap.design.xml
index 8ee3e98da96..15ef2b844d9 100644
--- a/pkgtools/pkglint4/files/doc/chap.design.xml
+++ b/pkgtools/pkglint4/files/doc/chap.design.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: chap.design.xml,v 1.1 2015/11/25 16:42:21 rillig Exp $ -->
+<!-- $NetBSD: chap.design.xml,v 1.2 2017/10/02 14:41:21 wiz Exp $ -->
 
 <chapter id="design">
 <title>Design goals</title>
@@ -44,7 +44,7 @@
 
 	<para>There are only two cases of what the output of
 	&pkglint; is. One is a single line containing the text
-	<quote>looks fine.</quote>, the other is a list of diagnostics,
+	<quote>Looks fine.</quote>, the other is a list of diagnostics,
 	followed by a summary on the number of diagnostics.</para>
 
 	<para>If no warnings are printed, the single line <quote>looks
diff --git a/pkgtools/pkglint4/files/pkglint.t b/pkgtools/pkglint4/files/pkglint.t
index 13c56e61323..34f07a4d6b4 100644
--- a/pkgtools/pkglint4/files/pkglint.t
+++ b/pkgtools/pkglint4/files/pkglint.t
@@ -1,5 +1,5 @@
 #! @PERL@
-# $NetBSD: pkglint.t,v 1.1 2015/11/25 16:42:21 rillig Exp $
+# $NetBSD: pkglint.t,v 1.2 2017/10/02 14:41:21 wiz Exp $
 #
 
 require 'pkglint.pl';			# so we can test its internals
@@ -131,7 +131,7 @@ sub test_pkglint_main {
 	test_unit($unit, undef, 0, '^usage: pkglint ', '^$');
 
 	@ARGV = ('..');
-	test_unit($unit, undef, 0, '^looks fine', '^$');
+	test_unit($unit, undef, 0, '^Looks fine', '^$');
 
 	@ARGV = ('.');
 	test_unit($unit, undef, 1, '^ERROR:.+how to check', '^$');
@@ -167,7 +167,7 @@ EOT
 		},
 		'mail/getmail' => {
 			stdout_re => <<EOT,
-^looks fine\.\$
+^Looks fine\.\$
 EOT
 			stderr_re => undef,
 			exitcode => 0,