docs: re-word project messaging

[kevinohara80]

The previous paragraph was good but a little unclear. This fixes that.

[Fishrock123]

LGTM, though I think io.js looks nicer as io.js.

[kevinohara80]

@Fishrock123 done ^^

[rvagg]

"io.js" isn't a programatic name so I'm -1 on io.js, I'd hate for that to become the norm for how it's written

[Fishrock123]

Yeah Rod is correct, I'm just silly.

[kevinohara80]

@rvagg I just removed the back ticks. Agree that formatting should be reserved for programatic items.

[indutny]

@Fishrock123 @rvagg are we good with this?

[rvagg]

sure, the line breaks bother me but that's not a big deal

LGTM

[bnoordhuis]

I think this needs to be rebased anyway before it can be applied. @kevinohara80 If you could fix the line breaks while you are at it, that would be great.

[kevinohara80]

No problem. I'll do this today.

On Wednesday, Dec 10, 2014 at 7:43 AM, Ben Noordhuis notifications@github.com, wrote:

I think this needs to be rebased anyway before it can be applied. @kevinohara80 If you could fix the line breaks while you are at it, that would be great.

—
Reply to this email directly or view it on GitHub.

[kevinohara80]

@bnoordhuis @rvagg Rebased and removed whitespace to make it a single paragraph. Let me know if there's any other tweaks.

[bnoordhuis]

Sorry, I didn't notice it's spread out over multiple commits. Can you squash them and make the commit log conform to what is outlined in CONTRIBUTING.md? git log README.md shows examples. Thanks!

[kevinohara80]

@bnoordhuis My bad. Does this look good?

[bnoordhuis]

Looks great, Kevin. Landed in 6f1d0a8, thanks!