rails text been added before version

railties/guides/source/asset_pipeline.textile

@@ -32,7 +32,7 @@ h4. Main Features
 
 The first is to concatenate of assets. This is important in a production environment to reduce the number of requests that a client browser has to make to render a web page. While Rails already has a feature to concatenate these types of asset--by placing +:cache => true+ at the end of tags such as +javascript_include_tag+ and +stylesheet_link_tag+--, many people do not use it.
 
-The default behavior in 3.1 and onward is to concatenate all files into one master file each for JS and CSS, however you can separate files or groups of files if required (see below). In production an MD5 fingerprint is inserted into each filename.
+The default behavior in Rails 3.1 and onward is to concatenate all files into one master file each for JS and CSS, however you can separate files or groups of files if required (see below). In production an MD5 fingerprint is inserted into each filename.
 
 The second feature of the pipeline is to minify or compress. For CSS this usually involves removing whitespace and comments. For Javascript more complex processes can be applied.
 
@@ -42,7 +42,7 @@ The third feature is the ability to code these assets using another language, or
 
 h4. What is fingerprinting and why should I care?
 
-Fingerprinting is a technique where the filenames of content that is static or infrequently updated is altered to be unique to the content contained in the file. 
+Fingerprinting is a technique where the filenames of content that is static or infrequently updated is altered to be unique to the content contained in the file.
 
 When a filename is unique and based on its content, http headers can be set to encourage caches everywhere (at ISPs, in browsers) to keep there own copy of the content. When the content is updated, the fingerprint will change and the remote clients will request the new file. This is generally known as _cachebusting_.
 
@@ -57,8 +57,8 @@ This is the strategy adopted by the Rails asset pipeline.
 Rails old strategy was to append a query string to every asset linked with a built-in helper. In the source the generated code looked like this:
 
 <plain>
-/stylesheets/global.css?1309495796  
-</plain>  
+/stylesheets/global.css?1309495796
+</plain>
 
 This has several disadvantages:
 
@@ -308,3 +308,4 @@ h3. Making Your Library or Gem a Pre-Processor
 
 "You should be able to register [your gems] on Tilt and Sprockets will find them." - Josh
 Tilt: https://github.com/rtomayko/tilt
+