Skip to content
This repository
Browse code

Fix typos in Association Basics guide

  • Loading branch information...
commit 701bd838c5b9f71b41632f198ed440723cb477a3 1 parent f5b9ed4
Jaime Iniesta authored October 17, 2012

Showing 1 changed file with 5 additions and 5 deletions. Show diff stats Hide diff stats

  1. 10  guides/source/en/association_basics.md
10  guides/source/en/association_basics.md
Source Rendered
@@ -637,7 +637,7 @@ The `create_association` method returns a new object of the associated type. Thi
637 637
 
638 638
 #### Options for `belongs_to`
639 639
 
640  
-While Rails uses intelligent defaults that will work well in most situations, there may be times when you want to customize the behavior of the `belongs_to` association reference. Such customizations can easily be accomplished by passing options and scope blocks when you create the association. For example, this assocation uses two such options:
  640
+While Rails uses intelligent defaults that will work well in most situations, there may be times when you want to customize the behavior of the `belongs_to` association reference. Such customizations can easily be accomplished by passing options and scope blocks when you create the association. For example, this association uses two such options:
641 641
 
642 642
 ```ruby
643 643
 class Order < ActiveRecord::Base
@@ -932,7 +932,7 @@ The `create_association` method returns a new object of the associated type. Thi
932 932
 
933 933
 #### Options for `has_one`
934 934
 
935  
-While Rails uses intelligent defaults that will work well in most situations, there may be times when you want to customize the behavior of the `has_one` association reference. Such customizations can easily be accomplished by passing options when you create the association. For example, this assocation uses two such options:
  935
+While Rails uses intelligent defaults that will work well in most situations, there may be times when you want to customize the behavior of the `has_one` association reference. Such customizations can easily be accomplished by passing options when you create the association. For example, this association uses two such options:
936 936
 
937 937
 ```ruby
938 938
 class Supplier < ActiveRecord::Base
@@ -1143,7 +1143,7 @@ When you declare a `has_many` association, the declaring class automatically gai
1143 1143
 * `collection.build(attributes = {}, ...)`
1144 1144
 * `collection.create(attributes = {})`
1145 1145
 
1146  
-In all of these methods, `collection` is replaced with the symbol passed as the first argument to `has_many`, and `collection_singular` is replaced with the singularized version of that symbol.. For example, given the declaration:
  1146
+In all of these methods, `collection` is replaced with the symbol passed as the first argument to `has_many`, and `collection_singular` is replaced with the singularized version of that symbol. For example, given the declaration:
1147 1147
 
1148 1148
 ```ruby
1149 1149
 class Customer < ActiveRecord::Base
@@ -1286,7 +1286,7 @@ The `collection.create` method returns a new object of the associated type. This
1286 1286
 
1287 1287
 #### Options for `has_many`
1288 1288
 
1289  
-While Rails uses intelligent defaults that will work well in most situations, there may be times when you want to customize the behavior of the `has_many` association reference. Such customizations can easily be accomplished by passing options when you create the association. For example, this assocation uses two such options:
  1289
+While Rails uses intelligent defaults that will work well in most situations, there may be times when you want to customize the behavior of the `has_many` association reference. Such customizations can easily be accomplished by passing options when you create the association. For example, this association uses two such options:
1290 1290
 
1291 1291
 ```ruby
1292 1292
 class Customer < ActiveRecord::Base
@@ -1737,7 +1737,7 @@ The `collection.create` method returns a new object of the associated type. This
1737 1737
 
1738 1738
 #### Options for `has_and_belongs_to_many`
1739 1739
 
1740  
-While Rails uses intelligent defaults that will work well in most situations, there may be times when you want to customize the behavior of the `has_and_belongs_to_many` association reference. Such customizations can easily be accomplished by passing options when you create the association. For example, this assocation uses two such options:
  1740
+While Rails uses intelligent defaults that will work well in most situations, there may be times when you want to customize the behavior of the `has_and_belongs_to_many` association reference. Such customizations can easily be accomplished by passing options when you create the association. For example, this association uses two such options:
1741 1741
 
1742 1742
 ```ruby
1743 1743
 class Parts < ActiveRecord::Base

0 notes on commit 701bd83

Please sign in to comment.
Something went wrong with that request. Please try again.