docs: make method names linkable

Author: kenjis

user_guide_src/source/database/queries.rst

@@ -99,21 +99,30 @@ It's a very good security practice to escape your data before submitting
 it into your database. CodeIgniter has three methods that help you do
 this:
 
-#. **$db->escape()** This function determines the data type so
-   that it can escape only string data. It also automatically adds
-   single quotes around the data so you don't have to:
+1. $db->escape()
+================
 
-   .. literalinclude:: queries/009.php
+This function determines the data type so
+that it can escape only string data. It also automatically adds
+single quotes around the data so you don't have to:
 
-#. **$db->escapeString()** This function escapes the data passed to
-   it, regardless of type. Most of the time you'll use the above
-   function rather than this one. Use the function like this:
+.. literalinclude:: queries/009.php
 
-   .. literalinclude:: queries/010.php
+2. $db->escapeString()
+======================
 
 #. **$db->escapeLikeString()** This method should be used when
    strings are to be used in LIKE conditions so that LIKE wildcards
    ('%', '\_') in the string are also properly escaped.
+This function escapes the data passed to
+it, regardless of type. Most of the time you'll use the above
+function rather than this one. Use the function like this:
+
+.. literalinclude:: queries/010.php
+
+3. $db->escapeLikeString()
+==========================
+
 
 .. literalinclude:: queries/011.php
 
@@ -162,7 +171,8 @@ placeholders in the query:
 Handling Errors
 ***************
 
-**$db->error();**
+$db->error()
+============
 
 If you need to get the last error that has occurred, the ``error()`` method
 will return an array containing its code and message. Here's a quick
@@ -220,23 +230,26 @@ Other Methods
 
 In addition to these two primary methods, the prepared query object also has the following methods:
 
-**close()**
+close()
+-------
 
 While PHP does a pretty good job of closing all open statements with the database it's always a good idea to
 close out the prepared statement when you're done with it:
 
 .. literalinclude:: queries/020.php
 
-**getQueryString()**
+getQueryString()
+----------------
 
 This returns the prepared query as a string.
 
-**hasError()**
+hasError()
+----------
 
 Returns boolean true/false if the last ``execute()`` call created any errors.
 
-**getErrorCode()**
-**getErrorMessage()**
+getErrorCode() getErrorMessage()
+--------------------------------
 
 If any errors were encountered these methods can be used to retrieve the error code and string.
 
@@ -249,7 +262,8 @@ Internally, all queries are processed and stored as instances of
 the parameters, otherwise preparing the query, and storing performance
 data about its query.
 
-**getLastQuery()**
+getLastQuery()
+==============
 
 When you just need to retrieve the last Query object, use the
 getLastQuery() method:
@@ -263,7 +277,8 @@ Each query object stores several pieces of information about the query itself.
 This is used, in part, by the Timeline feature, but is available for your use
 as well.
 
-**getQuery()**
+getQuery()
+----------
 
 Returns the final query after all processing has happened. This is the exact
 query that was sent to the database:
@@ -274,42 +289,48 @@ This same value can be retrieved by casting the Query object to a string:
 
 .. literalinclude:: queries/023.php
 
-**getOriginalQuery()**
+getOriginalQuery()
+------------------
 
 Returns the raw SQL that was passed into the object. This will not have any
 binds in it, or prefixes swapped out, etc:
 
 .. literalinclude:: queries/024.php
 
-**hasError()**
+hasError()
+----------
 
 If an error was encountered during the execution of this query this method
 will return true:
 
 .. literalinclude:: queries/025.php
 
-**isWriteType()**
+isWriteType()
+-------------
 
 Returns true if the query was determined to be a write-type query (i.e.,
 INSERT, UPDATE, DELETE, etc):
 
 .. literalinclude:: queries/026.php
 
-**swapPrefix()**
+swapPrefix()
+------------
 
 Replaces one table prefix with another value in the SQL. The first
 parameter is the original prefix that you want replaced, and the second
 parameter is the value you want it replaced with:
 
 .. literalinclude:: queries/027.php
 
-**getStartTime()**
+getStartTime()
+--------------
 
 Gets the time the query was executed in seconds with microseconds:
 
 .. literalinclude:: queries/028.php
 
-**getDuration()**
+getDuration()
+-------------
 
 Returns a float with the duration of the query in seconds with microseconds: