From: Varsha Rao <rvarsha016@gmail.com>
To: pablo@netfilter.org, netfilter-devel@vger.kernel.org
Cc: Varsha Rao <rvarsha016@gmail.com>
Subject: [PATCH nft] man: Fix typo.
Date: Sun, 6 Aug 2017 16:44:21 +0530 [thread overview]
Message-ID: <20170806111421.5754-1-rvarsha016@gmail.com> (raw)
The word 'occur' is misspelled as 'ocurr'. This patch fixes it.
Signed-off-by: Varsha Rao <rvarsha016@gmail.com>
---
doc/nft.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/nft.xml b/doc/nft.xml
index 4d03a3d..8ffa5b3 100644
--- a/doc/nft.xml
+++ b/doc/nft.xml
@@ -4381,7 +4381,7 @@ add rule nat prerouting tcp dport 22 redirect to :2222
<para>
The monitor command allows you to listen to Netlink events produced
by the nf_tables subsystem, related to creation and deletion of objects.
- When they ocurr, nft will print to stdout the monitored events in either
+ When they occur, nft will print to stdout the monitored events in either
XML, JSON or native nft format.
</para>
<para>
--
2.13.3
next reply other threads:[~2017-08-06 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 11:14 Varsha Rao [this message]
2017-08-14 9:42 ` [PATCH nft] man: Fix typo 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=20170806111421.5754-1-rvarsha016@gmail.com \
--to=rvarsha016@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).