|author||Guy Harris <email@example.com>||2015-11-10 13:07:54 -0800|
|committer||Guy Harris <firstname.lastname@example.org>||2015-11-10 21:08:45 +0000|
Apple calls it just "OS X" these days.
Change-Id: I98905988ceb394d27307d1cbe883d8fe95ac23e4 Reviewed-on: https://code.wireshark.org/review/11703 Reviewed-by: Guy Harris <email@example.com>
Diffstat (limited to 'help')
1 files changed, 2 insertions, 2 deletions
diff --git a/help/faq.py b/help/faq.py
index 692ee4b8d3..3575204fbf 100755
@@ -729,7 +729,7 @@ with version 4.2.2 or a later version.
-I've installed Wireshark from Fink on Mac OS X; why is it very slow to
+I've installed Wireshark from Fink on OS X; why is it very slow to
@@ -1204,7 +1204,7 @@ Most OSes do <strong>not</strong> support capturing the FCS of a frame
on Ethernet, and probably do not support it on most other link-layer
types. Some drivres on some OSes do support it, such as some (all?)
Ethernet drivers on NetBSD and possibly the driver for Apple's gigabit
-Ethernet interface in Mac OS X; in those OSes, you might always get the
+Ethernet interface in OS X; in those OSes, you might always get the
FCS, or you might only get the FCS if you capture in promiscuous mode
(you'd have to determine which is the case).