  The resulting API changes are further detailed below.
  
  #### The `.create()` and `.update()` methods.
  
  The `.restore_object()` method is now replaced with two seperate methods, `.create()` and `.update()`.
  
  When using the `.create()` and `.update()` methods you should both create *and save* the object instance. This is in contrast to the previous `.restore_object()` behavior that would instantiate the object but not save it.
  
  The following example from the tutorial previously used `restore_object()` to handle both creating and updating object instances.
  
 
</s> remove We now have a better seperation, with seperate `required` and `allow_none` arguments.
 </s> add We now have a better separation, with separate `required` and `allow_none` arguments. </s> remove * Some data, such as many-to-many relationships, cannot be added to the object instance until after it has been saved. This type of data needed to be hidden in some undocumentated state on the object instance, or kept as state on the serializer instance so that it could be used when `.save()` is called.
 </s> add * Some data, such as many-to-many relationships, cannot be added to the object instance until after it has been saved. This type of data needed to be hidden in some undocumented state on the object instance, or kept as state on the serializer instance so that it could be used when `.save()` is called. </s> remove * There can be complex dependancies involved in order of saving multiple related model instances.
 </s> add * There can be complex dependencies involved in order of saving multiple related model instances. </s> remove Removing the shortcut takes away an unneccessary layer of abstraction, and makes your codebase more explicit without any significant extra complexity. It also results in better consistency, as there's now only one way to set the serializer class and queryset attributes for the view, instead of two.
 </s> add Removing the shortcut takes away an unnecessary layer of abstraction, and makes your codebase more explicit without any significant extra complexity. It also results in better consistency, as there's now only one way to set the serializer class and queryset attributes for the view, instead of two. </s> remove This gives us better seperation of concerns, allows us to use single-step
 </s> add This gives us better separation of concerns, allows us to use single-step
The `.restore_object()` method is now replaced with two separate methods, `.create()` and `.update()`.
  The resulting API changes are further detailed below.
  
  #### The `.create()` and `.update()` methods.
  
The `.restore_object()` method is now replaced with two separate methods, `.create()` and `.update()`.
  
  When using the `.create()` and `.update()` methods you should both create *and save* the object instance. This is in contrast to the previous `.restore_object()` behavior that would instantiate the object but not save it.
  
  The following example from the tutorial previously used `restore_object()` to handle both creating and updating object instances.
  
keep keep keep keep replace keep keep keep keep keep
 Minor: fix spelling and grammar, mostly in 3.0 announcement 
docs/topics/3.0-announcement.md