Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Merge pull request #7 from philtr/typos

Fix a couple of typos
  • Loading branch information...
commit 719c79c04e37da0a2008630af094c1a60c811b8b 2 parents 96a2f92 + 3186eca
@bbatsov bbatsov authored
Showing with 4 additions and 4 deletions.
  1. +4 −4 README.md
View
8 README.md
@@ -1,7 +1,7 @@
# Abstract
The goal of this guide is to present a set of best practices and style
-prescriptions for Ruby on Rails 3 development. It's a complimentary
+prescriptions for Ruby on Rails 3 development. It's a complementary
guide to the already existing community-driven
[Ruby coding style guide](https://github.com/bbatsov/ruby-style-guide).
@@ -369,7 +369,7 @@ on including some little-known gem you should do a careful review of
its source code first.
* Do not remove the `Gemfile.lock` from version control. This is not
some randomly generated file - it makes sure that all of your team
- members get the same gem versions when they go a `bundle install`.
+ members get the same gem versions when they do a `bundle install`.
## Managing processes
@@ -380,8 +380,8 @@ its source code first.
# Testing Rails applications
The best approach to implementing new features is probably the BDD
-approach. You start out by writing some high level feature tests (
-generally written using Cucumber ), then you use these tests to drive
+approach. You start out by writing some high level feature tests
+(generally written using Cucumber), then you use these tests to drive
out the implementation of the feature. First you write view specs for
the feature and use those specs to create the relevant
views. Afterwards you create the specs for the controller(s) that will
Please sign in to comment.
Something went wrong with that request. Please try again.