- Patch #349504 by keith.smith: clean up sentence spacing in code comments.

1 files changed, 6 insertions, 6 deletions

diff --git a/includes/database/log.inc b/includes/database/log.inc
index 11ba2c57d..e25863bfb 100644
--- a/includes/database/log.inc
+++ b/includes/database/log.inc
@@ -11,7 +11,7 @@
  *
  * We log queries in a separate object rather than in the connection object
  * because we want to be able to see all queries sent to a given database, not
- * database target.  If we logged the queries in each connection object we
+ * database target. If we logged the queries in each connection object we
  * would not be able to track what queries went to which target.
  *
  * Every connection has one and only one logging object on it for all targets
@@ -20,7 +20,7 @@
 class DatabaseLog {
 
   /**
-   * Cache of logged queries.  This will only be used if the query logger is enabled.
+   * Cache of logged queries. This will only be used if the query logger is enabled.
    *
    * The structure for the logging array is as follows:
    *
@@ -58,7 +58,7 @@ class DatabaseLog {
    * If the specified logging key is already running this method does nothing.
    *
    * @param $logging_key
-   *   The identification key for this log request.  By specifying different
+   *   The identification key for this log request. By specifying different
    *   logging keys we are able to start and stop multiple logging runs
    *   simultaneously without them colliding.
    */
@@ -83,7 +83,7 @@ class DatabaseLog {
   /**
    * Empty the query log for the specified logging key.
    *
-   * This method does not stop logging, it simply clears the log.  To stop
+   * This method does not stop logging, it simply clears the log. To stop
    * logging, use the end() method.
    *
    * @param $logging_key
@@ -129,14 +129,14 @@ class DatabaseLog {
    * Determine the routine that called this query.
    *
    * We define "the routine that called this query" as the first entry in
-   * the call stack that is not inside includes/database.  That makes the
+   * the call stack that is not inside includes/database. That makes the
    * climbing logic very simple, and handles the variable stack depth caused
    * by the query builders.
    *
    * @link http://www.php.net/debug_backtrace
    * @return
    *   This method returns a stack trace entry similar to that generated by
-   *   debug_backtrace().  However, it flattens the trace entry and the trace
+   *   debug_backtrace(). However, it flattens the trace entry and the trace
    *   entry before it so that we get the function and args of the function that
    *   called into the database system, not the function and args of the
    *   database call itself.