From: Ben Gamari <ben@smart-cactus.org>
To: netfilter@vger.kernel.org
Subject: Minor language issues in documentation
Date: Tue, 16 Sep 2014 12:56:24 -0400 [thread overview]
Message-ID: <87vbon33nr.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]
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!
Cheers,
- Ben
[1] http://www.netfilter.org/projects/nftables/
[2] http://wiki.nftables.org/wiki-nftables/index.php/Main_differences_with_iptables
[3] http://wiki.nftables.org/wiki-nftables/index.php/Configuring_tables
[-- Attachment #2: Type: application/pgp-signature, Size: 472 bytes --]
next reply other threads:[~2014-09-16 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 16:56 Ben Gamari [this message]
2014-09-17 8:54 ` Minor language issues in documentation Pablo Neira Ayuso
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=87vbon33nr.fsf@gmail.com \
--to=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.