it's Active Record not ActiveRecord

/cc @fxn

1 files changed, 1 insertions, 1 deletions

diff --git a/guides/source/configuring.md b/guides/source/configuring.md
index df3d22debe..e253d639d4 100644
--- a/guides/source/configuring.md
+++ b/guides/source/configuring.md
@@ -729,7 +729,7 @@ development:
   timeout: 5000
 ```
 
-Since the connection pooling is handled inside of ActiveRecord by default, all application servers (Thin, mongrel, Unicorn etc.) should behave the same. Initially, the database connection pool is empty and it will create additional connections as the demand for them increases, until it reaches the connection pool limit.
+Since the connection pooling is handled inside of Active Record by default, all application servers (Thin, mongrel, Unicorn etc.) should behave the same. Initially, the database connection pool is empty and it will create additional connections as the demand for them increases, until it reaches the connection pool limit.
 
 Any one request will check out a connection the first time it requires access to the database, after which it will check the connection back in, at the end of the request, meaning that the additional connection slot will be available again for the next request in the queue.