[website] 01/01: Add spellcheck target to publish dependencies.

[Bas Couwenberg]

This is an automated email from the git hooks/post-receive script.

sebastic pushed a commit to branch master
in repository website.

commit 1c06a2b88d1efb500e1df9a78be27b7d02183fa9
Author: Bas Couwenberg <sebastic at xs4all.nl>
Date:   Thu Jul 7 21:38:42 2016 +0200

    Add spellcheck target to publish dependencies.
    
    Fix spelling errors with codespell.
---
 Makefile   | 8 +++++++-
 policy.xml | 4 ++--
 2 files changed, 9 insertions(+), 3 deletions(-)

diff --git a/Makefile b/Makefile
index 8fa19ee..c84f69c 100644
--- a/Makefile
+++ b/Makefile
@@ -3,7 +3,7 @@ PUBLISHDIR=/home/groups/pkg-grass/htdocs
 
 all: policy
 
-policy: valid
+policy: valid spellcheck
 	xsltproc \
 		--param toc.section.depth 3 \
 		--param toc.max.depth 2 \
@@ -21,6 +21,12 @@ clean:
 valid:
 	xmllint --valid --noout policy.xml
 
+spellcheck:
+	codespell policy.xml
+
+spellcheck-fix:
+	codespell -w -s policy.xml
+
 publish: policy
 	rsync -av .gitignore .htaccess * $(PUBLISHHOST):$(PUBLISHDIR) || true
 	ssh $(PUBLISHHOST) "chmod -R g+w $(PUBLISHDIR)/*" || true
diff --git a/policy.xml b/policy.xml
index 612d365..83cc62b 100644
--- a/policy.xml
+++ b/policy.xml
@@ -1291,7 +1291,7 @@ DIST=<replaceable><distribution></replaceable> ARCH=<replaceable><archi
               existing files.
             </para>
             <para>
-              It may also be helpfull to review the copyright file generated
+              It may also be helpful to review the copyright file generated
               by <command>licensecheck2dep5</command> for the new upstream
               release, and compared it to the existing
               <filename>debian/copyright</filename> file.
@@ -2004,7 +2004,7 @@ lintian ../build-area/*changes
         was created where UbuntuGIS developers are injecting their packaging
         straight into the Debian GIS version control system.
         To make sure that there will be no conflicts with the Debian revisions
-        some attention should be payed to the revision numbering.
+        some attention should be paid to the revision numbering.
         If the derivative is creating a new package (either from scratch or an
         upgraded version) it should get the version
         <code><upstreamversion>-0<derivativename><derivativerevision></code>

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-grass/website.git