diff options
| author | Ulf Lamping <ulf.lamping@web.de> | 2006-08-27 11:46:02 +0000 |
|---|---|---|
| committer | Ulf Lamping <ulf.lamping@web.de> | 2006-08-27 11:46:02 +0000 |
| commit | 11c289ecc31f465d18a86907860ebfdf361648ab (patch) | |
| tree | 3e8b38a85790d17fa08a1ea7a409992d915ba00d | |
| parent | 36d80b8c8b07a800e831e8b1cc7be7b863845fb6 (diff) | |
fix #1063, some leftover typo's: Etheral -> Wireshark
svn path=/trunk/; revision=19053
| -rw-r--r-- | doc/README.capture | 2 | ||||
| -rw-r--r-- | docbook/wsug_src/WSUG_app_howitworks.xml | 2 | ||||
| -rw-r--r-- | help/capturing.txt | 2 |
3 files changed, 3 insertions, 3 deletions
diff --git a/doc/README.capture b/doc/README.capture index 855a642cc4..ecde56ca8a 100644 --- a/doc/README.capture +++ b/doc/README.capture @@ -38,7 +38,7 @@ conditions.h Capture driver -------------- -Etheral doesn't have direct access to the capture hardware. Instead of this, +Wireshark doesn't have direct access to the capture hardware. Instead of this, it uses the Libpcap/Winpcap library to capture data from network cards. On Win32, in capture-wpcap.c the function g_module_open("wpcap") is called diff --git a/docbook/wsug_src/WSUG_app_howitworks.xml b/docbook/wsug_src/WSUG_app_howitworks.xml index b3180db833..cde9d5d639 100644 --- a/docbook/wsug_src/WSUG_app_howitworks.xml +++ b/docbook/wsug_src/WSUG_app_howitworks.xml @@ -11,7 +11,7 @@ <section><title>Program start</title> <para> - When Etheral starts, a lot of things are done: + When Wireshark starts, a lot of things are done: <itemizedlist> <listitem> initialize the dissectors (register the protocol tree), including plugins diff --git a/help/capturing.txt b/help/capturing.txt index b737eec6d1..5d297536ed 100644 --- a/help/capturing.txt +++ b/help/capturing.txt @@ -53,7 +53,7 @@ High performance capturing -------------------------- When your network traffic is high, you might need to take some steps to ensure Wireshark doesn't get behind on its capture, particularly if you're running it on a slow computer. -When Etheral cannot keep up, packets are dropped. To help avoid this as much as possible: +When Wireshark cannot keep up, packets are dropped. To help avoid this as much as possible: a) Don't use the "Update list of packets in real time" option (see above). This has a significant performance penalty. |