From: Ralph Dolmans <ralph@nlnetlabs.nl>
Date: Mon, 9 Sep 2019 16:54:23 +0000 (+0200)
Subject: Typo fix, reported by jpmens
X-Git-Tag: release-1.10.0rc1~28^2~25
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f3dfb4d537b2c9e8cbc32a61efde6ff60d342fd3;p=thirdparty%2Funbound.git

Typo fix, reported by jpmens
---

diff --git a/doc/unbound.conf.5.in b/doc/unbound.conf.5.in
index 5db810451..0a7e75db4 100644
--- a/doc/unbound.conf.5.in
+++ b/doc/unbound.conf.5.in
@@ -2086,7 +2086,7 @@ Response Policy Zones are configured with \fBrpz:\fR, and each one must have a
 \fBname:\fR. There can be multiple ones, by listing multiple rpz clauses, each
 with a different name. RPZ clauses are applied in order of configuration. The
 \fBrespip\fR module needs to be added to the \fBmodule-config\fR, e.g.:
-\fBmodule-config: "respip validator itarator"\fR.
+\fBmodule-config: "respip validator iterator"\fR.
 .P
 Only the QNAME and Response IP Address triggers are supported. The supported RPZ
 actions are: NXDOMAIN, NODATA, PASSTHRU, DROP and Local Data. RPZ QNAME triggers