@@ -307,7 +307,7 @@ module ClassMethods
307
307
# [:allow_destroy]
308
308
# If true, destroys any members from the attributes hash with a
309
309
# <tt>_destroy</tt> key and a value that evaluates to +true+
310
- # (e.g. 1, '1', true, or 'true'). This option is off by default.
310
+ # (e.g. 1, '1', true, or 'true'). This option is false by default.
311
311
# [:reject_if]
312
312
# Allows you to specify a Proc or a Symbol pointing to a method
313
313
# that checks whether a record should be built for a certain attribute
@@ -332,11 +332,11 @@ module ClassMethods
332
332
# nested attributes are going to be used when an associated record already
333
333
# exists. In general, an existing record may either be updated with the
334
334
# new set of attribute values or be replaced by a wholly new record
335
- # containing those values. By default the +:update_only+ option is + false+
335
+ # containing those values. By default the +:update_only+ option is false
336
336
# and the nested attributes are used to update the existing record only
337
337
# if they include the record's <tt>:id</tt> value. Otherwise a new
338
338
# record will be instantiated and used to replace the existing one.
339
- # However if the +:update_only+ option is + true+ , the nested attributes
339
+ # However if the +:update_only+ option is true, the nested attributes
340
340
# are used to update the record's attributes always, regardless of
341
341
# whether the <tt>:id</tt> is present. The option is ignored for collection
342
342
# associations.
0 commit comments