From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Ben Gamari <ben@smart-cactus.org>
Cc: netfilter@vger.kernel.org
Subject: Re: Minor language issues in documentation
Date: Wed, 17 Sep 2014 10:54:06 +0200 [thread overview]
Message-ID: <20140917085406.GA5213@salvia> (raw)
In-Reply-To: <87vbon33nr.fsf@gmail.com>
On Tue, Sep 16, 2014 at 12:56:24PM -0400, Ben Gamari wrote:
>
> Hello all,
>
> While browsing the nftables documentation I noticed that the word
> "performance" is often misused in a variety of ways. For instance,
> on the main page[1],
>
> Fast lookups through performance data structures: The new syntax
> allows you to arrange you rule-set in a very performance way
> contrary to purely linear-list based filtering policies.
>
> The use in the first sentence might be acceptable as a colloquialism but
> really could be improved by replacing "performance" with "high
> performance".
>
> The second sentence is a bit more serious as it uses "performance", a
> noun, as an adjective. You might consider replacing this with
> "performance-oriented" or a similar rewrite. I've found this same
> mix-up in a few other places as well[2].
>
> I also noticed a couple other small issues,
>
> * [3] misspells "hybrid"
> * The "Basic operational" section of the documentation ToC would be
> named "Basic operation"
>
> Otherwise thanks for the great packet mangling framework and thorough
> documentation!
I have fixed what you indicated in the nftables wiki. Thanks.
prev parent reply other threads:[~2014-09-17 8:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 16:56 Minor language issues in documentation Ben Gamari
2014-09-17 8:54 ` Pablo Neira Ayuso [this message]
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=20140917085406.GA5213@salvia \
--to=pablo@netfilter.org \
--cc=ben@smart-cactus.org \
--cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.