Hi @jgorset, I like your idea about preserve backwards compatibility, nevertheless, it would be better to warn the user about the method's future deprecation. Something like this for example:

```ruby
def avaliable_for_participant?(participant)
   warn "[DEPRECATION] avaliable_for_participant? is deprecated. Please use available_for_participant? instead"
   available_for_participant?(participant)
end
```
If you want to change your Pull Request with this in mind, we'll merge it :-)  
Thank you for the notice.