netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neutron Soutmun <neo.neutron@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: kadlec@blackhole.kfki.hu
Subject: [PATCH] Fix grammar error in manpage
Date: Mon, 20 Jul 2015 17:21:56 +0700	[thread overview]
Message-ID: <20150720102156.GA4932@oxygen> (raw)

[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]

Refer to: https://bugs.launchpad.net/ubuntu/+source/lintian/+bug/608231

The "allows to" is a common grammar error which it will probably be
replaced by "allows one to" as a suggestion in above bug report page.

Signed-off-by: Neutron Soutmun <neo.neutron@gmail.com>
---
 src/ipset.8 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/ipset.8 b/src/ipset.8
index a718f98..d0d7ac0 100644
--- a/src/ipset.8
+++ b/src/ipset.8
@@ -321,7 +321,7 @@ ipset add foo 192.168.1.1/24 comment "allow access to SMB share on \\\\\\\\files
 the above would appear as: "allow access to SMB share on \\\\fileserv\\"
 .PP
 .SS "skbinfo, skbmark, skbprio, skbqueue"
-All set types support the optional \fBskbinfo\fR extension. This extension allow to
+All set types support the optional \fBskbinfo\fR extension. This extension allows you to
 store the metainfo (firewall mark, tc class and hardware queue) with every entry and map it to
 packets by usage of SET netfilter target with \-\-map\-set option.
 \fBskbmark\fR option format: \fBMARK\fR or \fBMARK/MASK\fR, where \fBMARK\fR and \fBMASK\fR are 32bit hex
-- 
2.1.4


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2015-07-20 10:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 10:21 Neutron Soutmun [this message]
2015-07-20 12:03 ` [PATCH] Fix grammar error in manpage Jozsef Kadlecsik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150720102156.GA4932@oxygen \
    --to=neo.neutron@gmail.com \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=netfilter-devel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).