Fix READMEs (closes #2680) [coffee2code]

git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@2908 5ecf4fe2-1ee6-0310-87b1-e25e094e27de

1 files changed, 7 insertions, 7 deletions

diff --git a/actionpack/README b/actionpack/README
index c8624bf407..dc475a6610 100755
--- a/actionpack/README
+++ b/actionpack/README
@@ -24,14 +24,14 @@ ActiveRecord[http://activerecord.rubyonrails.org] (an object-relational
 mapping package), but that doesn't mean that Action Pack depends on Active
 Record. Action Pack is an independent package that can be used with any sort
 of backend (Instiki[http://www.instiki.org], which is based on an older version
-of Action Pack, uses Madeleine for example). Read more about the role Action
+of Action Pack, used Madeleine for example). Read more about the role Action
 Pack can play when used together with Active Record on
 http://www.rubyonrails.org.
 
 A short rundown of the major features:
 
 * Actions grouped in controller as methods instead of separate command objects
-  and can therefore helper share methods.
+  and can therefore share helper methods.
 
     BlogController < ActionController::Base
       def display
@@ -103,15 +103,15 @@ A short rundown of the major features:
       def list
         # Before this action is run, the user will be authenticated, the cache
         # will be examined to see if a valid copy of the results already
-        # exist, and the action will be logged for auditing.
+        # exists, and the action will be logged for auditing.
         
         # After this action has run, the output will first be localized then 
-        # compressed to minimize bandwith usage
+        # compressed to minimize bandwidth usage
       end
       
       private
         def authenticate
-          # Implement the filter will full access to both request and response
+          # Implement the filter with full access to both request and response
         end
     end
   
@@ -316,7 +316,7 @@ A short rundown of the major features:
 
     <%= form "post" %>
     
-    ...will generate something like (the selects will have more options of
+    ...will generate something like (the selects will have more options, of
     course):
     
     <form action="create" method="POST">
@@ -413,7 +413,7 @@ And the templates look like this:
   
 This simple setup will list all the posts in the system on the index page,
 which is called by accessing /weblog/. It uses the form builder for the Active
-Record model to make the new screen, which in turns hand everything over to
+Record model to make the new screen, which in turn hands everything over to
 the create action (that's the default target for the form builder when given a
 new model). After creating the post, it'll redirect to the display page using
 an URL such as /weblog/display/5 (where 5 is the id of the post).