some doc changes

docs/source/get-started/_deploy-the-documentation.md

@@ -1,3 +1,3 @@
-To update the documentation site, just make sure you have push access to the `Esri/calcite-web` repository and type `grunt deploy`. This will build the site and deploy to gh-pages.
+To update the documentation site, just make sure you have push access to the `Esri/calcite-web` repo and type `grunt deploy`. This will build the site and deploy to gh-pages.
 
-The site should be updated at http://esri.github.io/calcite-web/ in just a few moments.
+The site should be updated at http://esri.github.io/calcite-web/ in just a few moments.

docs/source/get-started/_get-started.md

@@ -6,10 +6,11 @@ Calcite Web was built *for* developers. It is meant to be flexible enough that y
 
 ## Using Calcite Web
 
-There are two main ways to use Calcite Web:
+There are three ways to use Calcite Web:
 
 - (a) copying static files into your project
 - (b) installing via a package manager
+- (c) loading files from the cdn
 
 Using this framework as a Sass library will give you the most power, but whatever your flavor, we have you covered.
 

docs/source/get-started/_versioning.md

@@ -19,8 +19,3 @@ The final number signifies patches such as fixing a pattern or component in a ce
 3. Make sure `Esri/calcite-web` is up-to-date with your changes.
 5. Run `grunt release`. If prompted enter your GitHub credentials and your s3 access key/secret.
 
-# Updating the Documentation Site
-
-To update the documentation site, just make sure you have push access to the `Esri/calcite-web` repo and type `grunt deploy`. This will build the site and deploy to gh-pages.
-
-The site should be updated at http://esri.github.io/calcite-web/ in just a few moments.