forked from osmocom/wireshark
Fix some typos detected in man pages.
parent
07ad7843f6
commit
38d77e6c7c
|
@ -1565,7 +1565,7 @@ MGCP packets exchanged by the host at IP address 1.2.3.4 .
|
|||
|
||||
Collect credentials (username/passwords) from packets. The report includes
|
||||
the packet number, the protocol that had that credential, the username and
|
||||
the password. For protocols just using one sigle field as authentication,
|
||||
the password. For protocols just using one single field as authentication,
|
||||
this is provided as a password and a placeholder in place of the user.
|
||||
|
||||
=item B<-z> proto,colinfo,I<filter>,I<field>
|
||||
|
|
|
@ -69,7 +69,7 @@ Save captured packet to file or send it through pipe.
|
|||
|
||||
=item --port=E<lt>portE<gt>
|
||||
|
||||
Set the listerner port. Port 5555 is the default.
|
||||
Set the listener port. Port 5555 is the default.
|
||||
|
||||
=item --payload=E<lt>typeE<gt>
|
||||
|
||||
|
|
|
@ -282,7 +282,7 @@ one byte). This is not allowed for byte sequences greater than one byte,
|
|||
because then one would need to specify the endianness of the multi-byte
|
||||
integer. Also, this is not allowed for decimal numbers, since they
|
||||
would be confused with hex numbers that are already allowed as
|
||||
byte strings. Neverthelss, single-byte hex integers can be convienent:
|
||||
byte strings. Nevertheless, single-byte hex integers can be convenient:
|
||||
|
||||
frame[4] == 0xff
|
||||
|
||||
|
|
Loading…
Reference in New Issue