Update the Cesium and Babylon engines

* Updated Cesium engine to 1.34 and leveraged the new [`basepath`](CesiumGS/cesium#5320) option in `Cesium.Model.fromGltf`.
* Updated Babylon.js engine to get a [tangent fix](BabylonJS/Babylon.js#2222).

Resolves Issue AnalyticalGraphicsInc#15

CHANGELOG.md

@@ -1,5 +1,10 @@
 # Change Log
 
+### 2.0.2 - UNRELEASED
+
+* Updated Cesium engine to 1.34 and leveraged the new [`basepath`](https://github.com/AnalyticalGraphicsInc/cesium/issues/5320) option in `Cesium.Model.fromGltf`.
+* Updated Babylon.js engine to get a [tangent fix](https://github.com/BabylonJS/Babylon.js/pull/2222).
+
 ### 2.0.1 - 2017-06-01
 
 * Update Babylon engine to fix glTF 1.0 support.

README.md

@@ -38,7 +38,7 @@ This works for arrays as well, for example the list of enabled render states.  H
 Press <kbd>ALT</kbd> + <kbd>G</kbd> on your glTF file, or look for the command `Preview 3D Model` in VSCode's list of commands (<kbd>CTRL</kbd> + <kbd>SHIFT</kbd> + <kbd>P</kbd>) and use that.
 
 The Babylon.js and Three.js engines will preview the saved model as opposed to
-the current content in your open VS Code tab.  The Cesium engine will first try
+the current content in your open VS Code tab.  The Cesium engines will first try
 to preview what is currently in your tab, and only if that fails will it fall
 back on displaying the version of the model saved on disk.