diff options
| author | Gerald Combs <gerald@wireshark.org> | 2023-01-08 17:52:00 -0800 |
|---|---|---|
| committer | Gerald Combs <gerald@wireshark.org> | 2023-01-09 18:00:11 +0000 |
| commit | 4d38cf9ec6053279c4ce70460b0528cf28e9c2c8 (patch) | |
| tree | f5b37f4a161f88fdce38e5d001de6fff34a4cc8f /docbook | |
| parent | 56deed1c158a45a21e3c918cb3ce31ea1fe0cdeb (diff) | |
FAQ: Fix some markup
Diffstat (limited to 'docbook')
| -rw-r--r-- | docbook/faq.adoc | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/docbook/faq.adoc b/docbook/faq.adoc index 801a863778..6a32d34119 100644 --- a/docbook/faq.adoc +++ b/docbook/faq.adoc @@ -632,9 +632,8 @@ Also, if at all possible, please send a copy of the capture file that caused the problem. When capturing packets, Wireshark normally writes captured packets to a temporary file, which will probably be in `/tmp` or `/var/tmp` on UNIX-flavored OSes, `\TEMP` on the main system disk -(normally `\Documents and Settings\`your login name -`\Local Settings\Temp` on the main system disk on Windows XP and -Server 2003, and `\Users\your login name\AppData\Local\Temp` on the main +(normally `\Documents and Settings\<your login name>\Local Settings\Temp` on the main system disk on Windows XP and +Server 2003, and `\Users\<your login name>\AppData\Local\Temp` on the main system disk on Windows Vista and later, so the capture file will probably be there. If you are capturing on a single interface, it will have a name of the form, |