This doesn't seem right to me...consider that in RSpec 3, `color()` does not behave the same as `color_enabled()` does in RSpec 2.x, so it seems wrong to tell the user the replacement is something that behaves differently.  Rather than giving them a deprecation warning that provides only one replacement which does does not behave the same, why not do this?

``` ruby
def color_enabled(output=output_stream)
  RSpec.deprecate("`RSpec::Core::Configuration#color_enabled`",
    :replacement => "`RSpec::Core::Configuration#color` (to see how the user has configured it) " +
    "or `RSpec::Core::Configuration#color_enabled?` (to see if RSpec will colorize the output)")
  color_enabled?(output)
end
```