Refactoring textual representation of specs

[m-a-r-c-e-l-i-n-o]

Hello, I don't mean to boggle anyone down with technicalities (no breakthroughs here), but I was wondering why the default textual output for the specs seem to lack a bit of consistency. If not for internal evaluation reasons, why not follow some sort of predicable format? Below are before and after images illustrating a possible improvement.

Before:

After:

For now, I've just made a few simple changes:

1. Maybe sure that every spec had a title corresponding to their filename.
2. Made sure that individual "it" blocks where surrounded by their respective method.
3. Made sure that all methods/functions were prefix by a "#" as intended on some of the specs.

I feel that this is important because it shows a clear distinction of where one test starts and another ends, and what subsection it pertains to. This would allow for a quicker analysis.

Unlike the rest, the "10_temperature_object_spec.rb" spec follows a very human-linguist style, so I left it mostly alone until further discussion.