caching.rb in actionpack-1.11.0

- old
+ new

@@ -16,11 +16,11 @@
         cattr_accessor :perform_caching
       end
     end
 
     # Page caching is an approach to caching where the entire action output of is stored as a HTML file that the web server 
-    # can serve without going through the Action Pack. This can be as much as 100 times faster than going the process of dynamically
+    # can serve without going through the Action Pack. This can be as much as 100 times faster than going through the process of dynamically
     # generating the content. Unfortunately, this incredible speed-up is only available to stateless pages where all visitors
     # are treated the same. Content management systems -- including weblogs and wikis -- have many pages that are a great fit
     # for this approach, but account-based systems where people log in and manipulate their own data are often less likely candidates.
     #
     # Specifying which actions to cache is done through the <tt>caches</tt> class method:
@@ -138,11 +138,11 @@
         end
     end
 
     # Action caching is similar to page caching by the fact that the entire output of the response is cached, but unlike page caching, 
     # every request still goes through the Action Pack. The key benefit of this is that filters are run before the cache is served, which
-    # allows for authentication and other restrictions on whether someone are supposed to see the cache. Example:
+    # allows for authentication and other restrictions on whether someone is allowed to see the cache. Example:
     #
     #   class ListsController < ApplicationController
     #     before_filter :authenticate, :except => :public
     #     caches_page   :public
     #     caches_action :show, :feed
@@ -226,11 +226,11 @@
     # == Fragment stores
     #
     # In order to use the fragment caching, you need to designate where the caches should be stored. This is done by assigning a fragment store
     # of which there are four different kinds:
     #
-    # * FileStore: Keeps the fragments on disk in the +cache_path+, which works well for all types of environments and share the fragments for
+    # * FileStore: Keeps the fragments on disk in the +cache_path+, which works well for all types of environments and shares the fragments for
     #   all the web server processes running off the same application directory.
     # * MemoryStore: Keeps the fragments in memory, which is fine for WEBrick and for FCGI (if you don't care that each FCGI process holds its
     #   own fragment store). It's not suitable for CGI as the process is thrown away at the end of each request. It can potentially also take
     #   up a lot of memory since each process keeps all the caches in memory.
     # * DRbStore: Keeps the fragments in the memory of a separate, shared DRb process. This works for all environments and only keeps one cache
@@ -254,11 +254,11 @@
           def self.fragment_cache_store=(store_option)
             store, *parameters = *([ store_option ].flatten)
             @@fragment_cache_store = if store.is_a?(Symbol)
               store_class_name = (store == :drb_store ? "DRbStore" : store.to_s.camelize)
               store_class = ActionController::Caching::Fragments.const_get(store_class_name)
-              parameters.empty? ? store.new : store_class.new(*parameters)
+              store_class.new(*parameters)
             else
               store
             end
           end
         end
@@ -479,17 +479,17 @@
     #       expire_action(:controller => "lists", :action => "all")
     #       list.shares.each { |share| expire_page(:controller => "lists", :action => "show", :id => share.url_key) }
     #     end
     #   end
     #
-    # The sweeper is assigned on the controllers that wish to have its job performed using the <tt>cache_sweeper</tt> class method:
+    # The sweeper is assigned in the controllers that wish to have its job performed using the <tt>cache_sweeper</tt> class method:
     #
     #   class ListsController < ApplicationController
     #     caches_action :index, :show, :public, :feed
     #     cache_sweeper :list_sweeper, :only => [ :edit, :destroy, :share ]
     #   end
     #
-    # In the example above, four actions are cached and three actions are responsible of expiring those caches.
+    # In the example above, four actions are cached and three actions are responsible for expiring those caches.
     module Sweeping
       def self.append_features(base) #:nodoc:
         super
         base.extend(ClassMethods)
       end