aboutsummaryrefslogtreecommitdiff
path: root/security/hafiye
diff options
context:
space:
mode:
authorJimmy Olgeni <olgeni@FreeBSD.org>2009-08-16 14:06:52 +0000
committerJimmy Olgeni <olgeni@FreeBSD.org>2009-08-16 14:06:52 +0000
commit0549f9a44f994c93ffd67b657690c7fe9dad43b7 (patch)
treefe67aa431033d3bf3b841080875c6139862a950a /security/hafiye
parent309a9ff76ae8736499a2071561927459b626ec1c (diff)
downloadports-0549f9a44f994c93ffd67b657690c7fe9dad43b7.tar.gz
ports-0549f9a44f994c93ffd67b657690c7fe9dad43b7.zip
Notes
Diffstat (limited to 'security/hafiye')
-rw-r--r--security/hafiye/pkg-descr2
1 files changed, 1 insertions, 1 deletions
diff --git a/security/hafiye/pkg-descr b/security/hafiye/pkg-descr
index 4b80ba1576b1..514f5e3c1d79 100644
--- a/security/hafiye/pkg-descr
+++ b/security/hafiye/pkg-descr
@@ -1,5 +1,5 @@
When I looked at the source code for various famous sniffers, I've noticed
-that they all had all seperate .C files for interpreting various protocols.
+that they all had all separate .C files for interpreting various protocols.
Why not have a sniffer that can understand user-supplied protocol details?
Here it is.