README.md in gem2rpm-0.11.2 vs README.md in gem2rpm-0.11.3

@@ -56,11 +56,11 @@
 ```
 
 Now you can edit the template and then run gem2rpm to generate the spec file using the edited template:
 
 ```
-$ gem2rpm -t rubygem-GEM.spec.template > rubygem-GEM.spec
+$ gem2rpm -t rubygem-GEM.spec.template GEM-1.2.3.gem > rubygem-GEM.spec
 ```
 
 With this new template you can now build your RPM as usual and when a new version of the gem becomes available, you just edit the saved template and rerun gem2rpm over it.
 
 To see all available templates that are shipped and can be directly used with gem2rpm run:
@@ -113,10 +113,10 @@
 The resulting RPMs should follow the naming convention 'rubygem-$GEM'
 where GEM is the name of the packaged gem. The default template also makes
 sure that the resulting package provides 'ruby($GEM)', according to general
 packaging conventions for scripting languages.
 
-## Limitiations
+## Limitations
 
 Because of the differences between the two packaging schemes, it is impossible to come up with a completely automated way of doing the conversion, but the spec files produced by this package should be good enough for most pure-ruby gems.
 
 ## See also