Description: <short summary of the patch>
 TODO: Put a short summary on the line above and replace this paragraph
 with a longer explanation of this change. Complete the meta-information
 with other relevant fields (see below for details). To make it easier, the
 information below has been extracted from the changelog. Adjust it or drop
 it.
 .
 clsync (0.4.2-1) unstable; urgency=medium
 .
   * New upstream release
   * Bump standards version
   * Harden
   * Fix some typos
Author: Barak A. Pearlmutter <bap@debian.org>

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: <vendor|upstream|other>, <url of original patch>
Bug: <url in upstream bugtracker>
Bug-Debian: https://bugs.debian.org/<bugnumber>
Bug-Ubuntu: https://launchpad.net/bugs/<bugnumber>
Forwarded: <no|not-needed|url proving that it has been forwarded>
Reviewed-By: <name and email of someone who approved the patch>
Last-Update: <YYYY-MM-DD>

--- clsync-0.4.2.orig/cluster.c
+++ clsync-0.4.2/cluster.c
@@ -486,7 +486,7 @@ static inline int cluster_read(int sock,
 	debug(30, "recvfrom(%i, %p, 0x%x, %p, %p) -> %i", sock, buf, MSG_WAITALL, &sa_in, &sa_in_len, readret);
 #ifdef PARANOID
 	if (!readret) {
-		error("recvfrom() returned 0. This shouldn't happend. Exit.");
+		error("recvfrom() returned 0. This shouldn't happen. Exit.");
 		return EINVAL;
 	}
 #endif
--- clsync-0.4.2.orig/man/man1/clsync.1
+++ clsync-0.4.2/man/man1/clsync.1
@@ -1090,7 +1090,7 @@ This monitor subsystem cannot determine
 determine a directory where something happened. So
 .B clsync
 is have to rescan whole dir every time on any content change. Moreover, kqueue
-requires an open() on every watched file/dir. But FreeBSD doesn't allow to
+requires an open() on every watched file/dir. But FreeBSD doesn't allow one to
 open() symlink itself (without following) and it's highly invasively to open()
 pipes and devices. So
 .B clsync
@@ -2455,7 +2455,7 @@ equals to 23 and you're using
 .B clsync
 in conjunction with
 .BR rsync ,
-this may happend, for example in next cases:
+this may happen, for example, in the following cases:
 
 .RS
 
@@ -2500,7 +2500,7 @@ tries to read next files (in specified o
 /etc/clsync/clsync.conf
 .RE
 
-This may be overrided with option
+This may be overridden with option
 .IR \-\-config\-file .
 
 .B clsync
--- clsync-0.4.2.orig/privileged.c
+++ clsync-0.4.2/privileged.c
@@ -632,7 +632,7 @@ int privileged_execvp_check_arguments(st
 	}
 
 	debug(1, "a_i == %i; SHARGS_MAX == %i; u_argc == %i", SHARGS_MAX, a_i, u_argc);
-	critical("Arguments are wrong. This should happend only on hacking attack.");
+	critical("Arguments are wrong. This should happen only on hacking attack.");
 	return EPERM;
 }
 
