STYLE:Fixed doxygen.

Author: fbertelatkitware

Filtering/vtkAbstractCellLocator.h

@@ -21,13 +21,13 @@
 // .SECTION Warning
 // When deriving a class from vtkAbstractCellLocator, one should include the 
 // 'hidden' member functions by the following construct in the derived class 
-// <verbatim>
+// \verbatim
 // //BTX
 //  using vtkAbstractCellLocator::IntersectWithLine;
 //  using vtkAbstractCellLocator::FindClosestPoint;
 //  using vtkAbstractCellLocator::FindClosestPointWithinRadius;
 // //ETX
-// </verbatim>
+// \endverbatim
 
 //
 // .SECTION See Also

Filtering/vtkCell.h

@@ -22,7 +22,7 @@
 // implicitly composed of cells (e.g., vtkStructuredPoints).
 //
 // .SECTION Caveats
-// The #define VTK_CELL_SIZE is a parameter used to construct cells and provide
+// The \#define VTK_CELL_SIZE is a parameter used to construct cells and provide
 // a general guideline for controlling object execution. This parameter is 
 // not a hard boundary: you can create cells with more points.
 

Hybrid/vtkCornerAnnotation.h

@@ -119,7 +119,7 @@ class VTK_HYBRID_EXPORT vtkCornerAnnotation : public vtkActor2D
   vtkGetObjectMacro(TextProperty,vtkTextProperty);
 
   // Description:
-  // Even if there is an image actor, should <slice> and <image> be displayed?
+  // Even if there is an image actor, should `slice' and `image' be displayed?
   vtkBooleanMacro(ShowSliceAndImage, int);
   vtkSetMacro(ShowSliceAndImage, int);
   vtkGetMacro(ShowSliceAndImage, int);

IO/vtkOffsetsManagerArray.h

@@ -18,13 +18,15 @@
 // in a file (unsigned long) and associate a offset in the file. This is
 // usefull when writing TimeStep XML file when you want to forward the 
 // same offset from the AppendData section on every entry in let say
-// <Points> definition
+// \<Points\> definition
 // Example:
+// \verbatim
 // <Points>
 //   <DataArray type="Float32" TimeStep="0" format="appended" offset="268" />
 //   <DataArray type="Float32" TimeStep="1" format="appended" offset="268" />
 //   ...
 // </Points>
+// \endverbatim
 // Therefore data is only stored once in the XML file. At read time the 
 // offset value is stored to determine whenever we need to read data 
 // (ie when offset different from previously stored offset)