summaryrefslogtreecommitdiff
path: root/includes/cache-install.inc
diff options
context:
space:
mode:
authorDries Buytaert <dries@buytaert.net>2011-02-19 00:09:11 +0000
committerDries Buytaert <dries@buytaert.net>2011-02-19 00:09:11 +0000
commitfa39282ef779a331ba2e3096f791c5a663994e16 (patch)
treecbbff5ddd220781bd7398e0531750a2e7404ee95 /includes/cache-install.inc
parent7205ff14cac0472acb9247297d13477ab9cc5a97 (diff)
downloadbrdo-fa39282ef779a331ba2e3096f791c5a663994e16.tar.gz
brdo-fa39282ef779a331ba2e3096f791c5a663994e16.tar.bz2
- Patch #1056108 by 1V: consistent use of 'JavaScript' and 'Ajax'.
Diffstat (limited to 'includes/cache-install.inc')
-rw-r--r--includes/cache-install.inc2
1 files changed, 1 insertions, 1 deletions
diff --git a/includes/cache-install.inc b/includes/cache-install.inc
index 545f1a2a2..8c47b001a 100644
--- a/includes/cache-install.inc
+++ b/includes/cache-install.inc
@@ -31,7 +31,7 @@ class DrupalFakeCache extends DrupalDatabaseCache implements DrupalCacheInterfac
// If there is a database cache, attempt to clear it whenever possible. The
// reason for doing this is that the database cache can accumulate data
// during installation due to any full bootstraps that may occur at the
- // same time (for example, AJAX requests triggered by the installer). If we
+ // same time (for example, Ajax requests triggered by the installer). If we
// didn't try to clear it whenever this function is called, the data in the
// cache would become stale; for example, the installer sometimes calls
// variable_set(), which updates the {variable} table and then clears the