Content revision

docs.it4i/anselm/software/debuggers/papi.md

@@ -90,19 +90,19 @@ The include path is automatically added by papi module to $INCLUDE.
 
 ### High Level API
 
-Please refer to <http://icl.cs.utk.edu/projects/papi/wiki/PAPIC:High_Level> for a description of the High level API.
+Please refer to [this description of the High level API](http://icl.cs.utk.edu/projects/papi/wiki/PAPIC:High_Level).
 
 ### Low Level API
 
-Please refer to <http://icl.cs.utk.edu/projects/papi/wiki/PAPIC:Low_Level> for a description of the Low level API.
+Please refer to [this description of the Low level API](http://icl.cs.utk.edu/projects/papi/wiki/PAPIC:Low_Level).
 
 ### Timers
 
-PAPI provides the most accurate timers the platform can support. See <http://icl.cs.utk.edu/projects/papi/wiki/PAPIC:Timers>
+PAPI provides the most accurate timers the platform can support. [See](http://icl.cs.utk.edu/projects/papi/wiki/PAPIC:Timers).
 
 ### System Information
 
-PAPI can be used to query some system infromation, such as CPU name and MHz. See <http://icl.cs.utk.edu/projects/papi/wiki/PAPIC:System_Information>
+PAPI can be used to query some system infromation, such as CPU name and MHz. [See](http://icl.cs.utk.edu/projects/papi/wiki/PAPIC:System_Information).
 
 ## Example
 
@@ -232,6 +232,6 @@ To use PAPI in offload mode, you need to provide both host and MIC versions of P
 
 ## References
 
-1. <http://icl.cs.utk.edu/papi/> Main project page
-1. <http://icl.cs.utk.edu/projects/papi/wiki/Main_Page> Wiki
-1. <http://icl.cs.utk.edu/papi/docs/> API Documentation
+1. [Main project page](http://icl.cs.utk.edu/papi/)
+1. [Wiki](http://icl.cs.utk.edu/projects/papi/wiki/Main_Page)
+1. [API Documentation](http://icl.cs.utk.edu/papi/docs/)