Currently links to https://mustache.github.com/ lead the user to a 404
page. With this correction they will be linked to https://mustache.github.io that is the expected page.

By showing explicitly how/where `Mustache` comes from in that
specific scenario, where CommonJS is assume to be available,
either provided by Node.js or a build tool like webpack etc.

For the record, it could also be `import` if the using project
uses ES Modules, as we've recently exposed native ES Modules
support as well.

There has not been activity there for several years. No point in
actively inviting potential using developers in there, instead of
just using what we have on GitHub.

If the key is false or empty

Blooper introduced when making the usage examples in README.md
more modern a couple of days ago, where the example fetching the
mustache template over HTTP, didn't in fact use the fetched template.

Since TypeScript usage has exploded the last years but this is
package is written in JavaScript, we might at least reference
the external DefinitelyTyped package @types/mustache that has
a somewhat up-to-date set of type definitions for most of the package.

Primarily because the these sections were very given a lot
of attention, high up in the README, where ideally usage and
basic syntax should have priority.

More and more of the community seems to be encouraging use of
zero-dependency packages. We might as well point that out early
on in our README since that's how mustache.js always has been
and planned to be going forward.

Primarily because [rtype](https://github.com/ericelliott/rtype) seems to
be a stalled project that hasn't gotten updated for 4 years.

Similar more up-to-date definitions can be found in the
TypeScript definitions: [@types/mustache](https://www.npmjs.com/package/@types/mustache).

When recently updating the usage examples in the README,
it blooper was introduced where `response.text()` was forgotten
when retrieving a mustache template with `window.fetch()`.

Historically jQuery was seen as an absolute minimal to create
anything with JavaScript. That time has past now that relatively
modern browsers has excellent support for a lot of the things
jQuery helped us with -- at least with the trivial examples shown
in our README.

Therefore removing jQuery usage from our examples as that should
not be a necessary dependency in these examples.

As Bower is deprecated a long time ago: https://bower.io/blog/2017/how-to-migrate-away-from-bower/

It does't make sense to mention it in the readme.

Because there has been a deliberate effort from the Node.js project
to use the term `Node.js` rather than anything else. It also helps beginners
by being more explicit and self-descriptive.

changed beard competition wiki link to the new link as the route has been changed.

In the README the return type for Mustache.parse is listed as a String. It's actually an array of Tokens.

Documents ways to set custom delimiters via JS, in addition to inline in the templates.

I couldn’t find the API in the docs. This is what I found out by reading the source. Let’s save others the pain.

Mark partials as optional

Add syntax highlighting style to previously missed code blocks

Past tense of "run" is "ran", not "runned".

fix local install

Fix order section and grammatical

Fix the comments

Fix command line mustache

* Although my previous PR (#469) on this topic was merged, it caused
  [quite a discussion](https://github.com/janl/mustache.js/pull/469) about
  the clarity of the language I wrote.
* This commit seeks to clarify and improve the sentence under discussion.

As secure $ENVs are disabled for pull requests and those $ENVs are required for running browser tests on saucelabs.

http://docs.travis-ci.com/user/pull-requests/#Security-Restrictions-when-testing-Pull-Requests

+ updated readme with the fact that browser tests are only runned automatically when *merged into master*, not in the PR stage

Covers the project with browser tests, not only V8 via node/iojs. Tests are runned with [zuul](https://github.com/defunctzombie/zuul) which
provides simple local browser testing, aswell as cloud testing on multiple browsers with [saucelabs](http://saucelabs.com).

CLI used to render a mustache template with a data view, writes the template into stdout when successfull. Otherwise meaningfull errors into stderr.

Fixes #424

- Documented required version of npm while developing
- Use the latest npm client for node >= v0.8 on travis

Special quirks to get node v0.6 supported:
	- npm client v1.3.26 on travis
	- jshint 2.4.4 as >= 2.5.x breaks