[docs] remove links to uploader

docs/core/asset-management-system.md

@@ -68,12 +68,10 @@ headers][cors] if the asset is on a different domain. Otherwise, we'd have
 to host assets on the same origin as the scene.
 
 [ghpages]: https://pages.github.com/
-[uploader]: https://cdn.aframe.io
 
-For some options, [GitHub Pages][ghpages] serves everything with CORS headers.
-We recommend GitHub Pages as a simple deployment platform.  Or you could also
-upload assets using the [A-Frame + Uploadcare Uploader][uploader], a service
-that serves files with CORS headers set.
+For other options, [GitHub Pages][ghpages] serves everything with CORS headers.
+We recommend GitHub Pages as a simple deployment platform. Or another service
+that serves files with CORS headers set (such as Amazon S3).
 
 [corsimage]: https://developer.mozilla.org/docs/Web/HTML/CORS_enabled_image
 

docs/introduction/hosting-and-publishing.md

@@ -117,7 +117,6 @@ scene. Plus, if we're using `<a-assets>`, we should usually set
 
 There are several simple options to host assets via a CDN:
 
-- [A-Frame Asset Uploader](https://cdn.aframe.io/) - Uses UploadCare.
 - [Glitch Asset Uploader](https://glitch.com/) - The Glitch code editor has a
   panel to upload assets and get CDN URLs in return.
 - [imgur](https://imgur.com/) - For images, we could use imgur, a popular image

examples/index.html

@@ -125,7 +125,6 @@ <h1>A-Frame Examples</h1>
         <li><a href="https://github.com/aframevr">GitHub</a></li>
         <li><a href="https://aframevr-slack.herokuapp.com/">Slack</a></li>
         <li><a href="https://twitter.com/aframevr">Twitter</a></li>
-        <li><a href="https://cdn.aframe.io">Asset Uploader</a></li>
         <li><a href="https://webvr.directory">Showcase Directory</a></li>
       </ul>
     </header>