F5/unison
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

a few more texi typos

Browse Source
This commit is contained in:
Josh Pelkey
2010-04-21 15:15:19 -04:00
parent f3a6c5ab08
commit 54ec7b22b8
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/manual/tracing.texi
View File

@@ -906,7 +906,7 @@ enumerated and tracing is enabled on the resulting pairs. For example,
@end verbatim
You can enable pcap tracing on the basis of node ID and interface as well. In
this case, the node-id is translated to a @code{Ptr{Node} and the appropriate
this case, the node-id is translated to a @code{Ptr<Node>} and the appropriate
protocol is looked up in the node. The resulting protocol and interface are
used to specify the resulting trace source.
@@ -1147,7 +1147,7 @@ follows the <prefix>-<node id>-<device id>.tr convention. Combining all of the
traces into a single file is accomplished similarly to the examples above:
You can enable pcap tracing on the basis of node ID and device ID as well. In
this case, the node-id is translated to a @code{Ptr{Node} and the appropriate
this case, the node-id is translated to a @code{Ptr<Node>} and the appropriate
protocol is looked up in the node. The resulting protocol and interface are
used to specify the resulting trace source.

4
doc/tutorial/tracing.texi
View File

@@ -2852,7 +2852,7 @@ enumerated and tracing is enabled on the resulting pairs. For example,
@end verbatim
You can enable pcap tracing on the basis of node ID and interface as well. In
this case, the node-id is translated to a @code{Ptr{Node} and the appropriate
this case, the node-id is translated to a @code{Ptr<Node>} and the appropriate
protocol is looked up in the node. The resulting protocol and interface are
used to specify the resulting trace source.
@@ -3101,7 +3101,7 @@ follows the <prefix>-<node id>-<device id>.tr convention. Combining all of the
traces into a single file is accomplished similarly to the examples above:
You can enable pcap tracing on the basis of node ID and device ID as well. In
this case, the node-id is translated to a @code{Ptr{Node} and the appropriate
this case, the node-id is translated to a @code{Ptr<Node>} and the appropriate
protocol is looked up in the node. The resulting protocol and interface are
used to specify the resulting trace source.