Guide could use some copy-editing and general TLC

[mrhota]

There are a number of small typos in the guide, and some of the prose could be tightened up or clarified.

In general the tone of the guide comes across as trying too hard to be chatty. Keeping things casual is probably a good idea for Rust's introductory document, but we can probably remove most (all?) of the chatty prose without becoming stodgy or boring.

[apasel422]

The guide is inconsistent with its use of certain conventions. These don't really have a correct form, but a single style should be enforced.

• Single-quotes (') versus double-quotes (") in prose. Example:

  The first thing we'll learn about are 'variable bindings.'

  Well, Rust has this thing called "type inference."

• Periods and commas within quotes versus without. Example:

  A struct is another form of a 'record type,'

  This operator is called 'modulo',

• "different from" versus "different than". Example:

  This is different from named functions

  Rust's macros are significantly different than C macros

• "filename" versus "file name"

[Gankra]

If you find any obvious errors, or think you can write a section in a better way, please don't hesitate to submit a PR with a fix. You don't need to compile a compiler or download the source to edit the guide. You can do it all in github's ui, for the most part.

[steveklabnik]

@apasel422 thanks for being specific. And for your earlier pull request. As for these...

• They should be double quotes. Ideally, they'd even be actual curlies rather than ".
• Periods and commas go within in almost all cases. In both of the cases you show, they should go inside.
• "Different from" vs. "Different than" isn't something that's generally settled. Some styles choose it in different situations, others say "from" is the only correct way to say this.
• "file name" is my preferred way, though there's no specific actual guidance.