Online documentation has lame interpolation failures

[twhaples]

At http://mime-types.rubyforge.org/MIME/Types.html#method-i-type_for there is sample code which looks like

puts "MIME::Types.type_for('citydesk.xml')
  => "#{MIME::Types.type_for('citydesk.xml')}"
puts "MIME::Types.type_for('citydesk.gif')
  => "#{MIME::Types.type_for('citydesk.gif')}"

Seriously? It's supposed to output a bunch of junk with a #{} around it? I don't think so.
Unfortunately, because the real sample output was missing when I looked, I assumed it would return a single type and tried to send something from Rails with :content_type => MIME::Types.type_for('foo.css') which sent the deceptively-good-looking string [text/css] instead of sending text/css. I subsequently wasted a bunch of time tracking down what the problem was.

[halostatue]

Fixed in 1.18.

irb is quite useful for this sort of thing if you find yourself confused again.