-Changing the default from /public helps avoid naming conflicts, since you may

-want to put other static html in /public, but changing this will require web

+Changing the default from +public+ helps avoid naming conflicts, since you may

+want to put other static html in +public+, but changing this will require web

server reconfiguration to let the web server know where to serve the cached

files from.

@@ -96,7 +96,7 @@ end

If you want a more complicated expiration scheme, you can use cache sweepers

to expire cached objects when things change. This is covered in the section on Sweepers.

-Note: Page caching ignores all parameters, so /products/list?page=1 will be written out to the filesystem as /products/list.html and if someone requests /products/list?page=2, they will be returned the same result as page=1, so be careful when page caching GET parameters in the URL!

+Note: Page caching ignores all parameters. For example +/products?page=1+ will be written out to the filesystem as +products.html+ with no reference to the +page+ parameter. Thus, if someone requests +/products?page=2+ later, they will get the cached first page. Be careful when page caching GET parameters in the URL!

h4. Action Caching

@@ -110,7 +110,7 @@ result of the output from a cached copy.

Clearing the cache works in the exact same way as with Page Caching.

-Let's say you only wanted authenticated users to call actions on the Products controller.

+Let's say you only wanted authenticated users to call actions on +ProductsController+.

<ruby>

class ProductsController < ActionController

@@ -136,12 +136,12 @@ or the number of items in the cart can be left uncached. This feature is

available as of Rails 2.2.

You can modify the default action cache path by passing a +:cache_path+ option.

-This will be passed directly to ActionCachePath.path_for. This is handy for

+This will be passed directly to +ActionCachePath.path_for+. This is handy for

actions with multiple possible routes that should be cached differently. If

a block is given, it is called with the current controller instance.

Finally, if you are using memcached, you can also pass +:expires_in+. In fact,

-all parameters not used by caches_action are sent to the underlying cache

+all parameters not used by +caches_action+ are sent to the underlying cache