--- a/doc/manual/tracing.texi	Wed Apr 21 15:07:34 2010 -0400
+++ b/doc/manual/tracing.texi	Wed Apr 21 15:15:19 2010 -0400
@@ -906,7 +906,7 @@
 @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 @@
 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.
 

--- a/doc/tutorial/tracing.texi	Wed Apr 21 15:07:34 2010 -0400
+++ b/doc/tutorial/tracing.texi	Wed Apr 21 15:15:19 2010 -0400
@@ -2852,7 +2852,7 @@
 @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 @@
 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.