This fixes a small blooper introduced in a3f4339.
Error message thrown for invalid template type, should be equal on
the server and in the browser.

Clarifies and improves language in documentation

* 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.

Update UMD Shim to be resilient to HTMLElement global pollution

Please see https://github.com/umdjs/umd/pull/63 and https://github.com/umdjs/umd/issues/35 for more information, but
this change prevents an HTML element with an id of `exports` from causing the UMD shim to incorrectly detect the environment as node.

Move gif to githubusercontent #327

Documents use of string literals containing double quotes

Throw error when providing .render() with invalid template type

As we require the template to be a `string` we now throw an error when given
any other data type. This should provide the developers with a meaningful
error rather than a cryptic TypeError from the murky depths of our source code.

Fixes #464

Added global Mustache definition

This reverts commit 2f51083565. Util is
not yet configurable, so issue links point to `mocha`.

`version` is currently a moot prop since git tags are used instead. More
info at https://github.com/bower/bower.json-spec/commit/a325da3.

Remove moot `version` property from bower.json

Per bower/bower.json-spec@a325da3

Fix view prototype value lookup issues

Fixes #445

Bugfix for view context cache

Fixes #442

Only display result of master branch on travis badge

Closes #450

Minor changes to make it compatible with both WSH and ASP (eslint com…

Added the keywords "imports", "nested" and "subtemplates" to the docs

Improve CLI parsing error

Made it eslint compatible.

Add license attribute

https://docs.npmjs.com/files/package.json#license
http://npm1k.org/

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

With 25 different browser versions it could easily take 15-25 minutes for a run too finish.
Only test latest chrome & firefox atm, increase support later as needed.

Removing hacks to get v0.6 tests running; specific npm client version + upgrading mocha.
Also v0.12 of node has been released, therefore there's no reason to still keep testing on v0.11.

Browser tests