README.md in jsonify-0.2.0 vs README.md in jsonify-0.3.0

@@ -37,11 +37,11 @@
 pretty printing is a relatively costly operation and should not be used in production (unless, of course, you explicitly
 want to show this format). The default format, `plain`, dictates no special formatting: the result will be rendered as a compact string without any newlines.
 
 ### Compatibility Warning
 
-Starting with version 0.2.0, the handling of arrays has changed to provide a more natural feel. As a consequence, however, code written using earlier versions of Jsonify may not work correctly. The example that follows demonstrates the changes you will need to be make.
+Starting with version 0.2.0, the handling of arrays has changed to provide a more natural feel. As a consequence, however, code written using earlier versions of Jsonify may not work correctly. The example that follows demonstrates the changes you need to make.
 
 Previously, when arrays were processed, you had to put away the builder-style, and use more conventional Rubyisms.
 
     json.links(@links) do |link|
       {:rel => link.type, :href => link.url}
@@ -151,10 +151,10 @@
 
     json << 1
     json.ingest! (render :partial=>'my_partial')
 
 From the first line, you can tell that an array will be created as this line uses the append operator.
-On the second line, a partial is being added to the builder. Note that you cannot simply place `render :parial ...` on a line by itself as you can do with other templates like `erb` and `haml`. You have to explicitly tell Jsonify to add it to the builder.
+On the second line, a partial is being added to the builder. Note that you cannot simply place `render :partial ...` on a line by itself as you can do with other templates like `erb` and `haml`. You have to explicitly tell Jsonify to add it to the builder.
 
 Let's say that the partial file, `_my_partial.jsonify`, is as follows:
 
     json << 3
     json << 4