diff --git a/docs/api/inferno-redux.md b/docs/api/inferno-redux.md
index f85f0c008..ef698b251 100644
--- a/docs/api/inferno-redux.md
+++ b/docs/api/inferno-redux.md
@@ -2,7 +2,7 @@
 title: Inferno Redux
 ---
 
-We understand that a lot of application in the React ecosystem use [Redux](//reduxjs.org) to manage data. Thus we have a created a port of React-Redux for Inferno to ease the process of porting an application over. 
+We understand that a lot of applications in the React ecosystem use [Redux](//reduxjs.org) to manage data. Thus we have created a port of React-Redux for Inferno to ease the process of porting an application over. 
 
 ## `Provider`
 
diff --git a/docs/api/inferno.md b/docs/api/inferno.md
index 2408976b0..98913a08e 100644
--- a/docs/api/inferno.md
+++ b/docs/api/inferno.md
@@ -110,22 +110,6 @@ If a component has been mounted into the DOM, this returns the corresponding nat
 
 **Note**: we recommend using a `ref` callback on a component to find its instance, rather than using `findDOMNode`. `findDOMNode` cannot be used on functional components.
 
-## createRenderer
-
-`createRenderer` allows for functional composition when rendering content to the DOM. An example of this is shown below:
-
-```javascript
-import Inferno from 'inferno';
-import { scan, map } from 'most';
-
-...
-const model$ = scan(update, 0, actions$);
-const vNodes$ = map(view(actions$), model$);
-const renderer = Inferno.createRenderer();
-const runApp = () => scan(renderer, container, vNodes$).drain();
-
-runApp();
-```
 
 ## disableRecycling
 As an application changes components will be reused as they are mounted and unmounted from the DOM. By default Inferno enables *recycling* to have a pool of components which can be reused when components are mounted into the DOM. However if you wish to disable this feature you can. 
diff --git a/docs/guides/get-started.md b/docs/guides/get-started.md
index cfe8cbb01..c14b67198 100644
--- a/docs/guides/get-started.md
+++ b/docs/guides/get-started.md
@@ -2,11 +2,11 @@
 title: Get Started
 ---
 
-There are three ways to get setup with Inferno, the simple `create-inferno-app`, installation via NPM, or using the Cloudfare CDN. 
+There are three ways to get setup with Inferno: using the simple `create-inferno-app`, installing via NPM, or by using the Cloudfare CDN.
 
 ## Create Inferno App
 
-Similarly to React you can get started by using `create-inferno-app`. Make sure that you have Node installed 
+Similar to React's `create-react-app`, you can get started by using `create-inferno-app`. Make sure that you have Node installed
 
 ```
 (sudo) npm install -g create-inferno-app
@@ -18,13 +18,18 @@ npm start
 Then navigate to [`http://localhost:8080/`](http://localhost:8080) to view the application.
 
 ## NPM Installation
-The core Inferno is packaged on NPM as `inferno`.
+Inferno is packaged on NPM as `inferno`.
 
 <div>
   `npm install inferno --save`
 </div>
 
-Which will set you up with the core package and everything you need to start creating components and rendering them, but you'll probably want to take a look at our [other packages]({{site.url}}/guides/architecture) for convenience. 
+This will set you up with the core package and everything you need to start creating components and rendering them, but you'll probably want to take a look at our [other packages]({{site.url}}/guides/architecture) for convenience.
 
 ## Cloudfare
 
+Pre-bundled files for browser consumption can be found on [our cdnjs](https://cdnjs.com/libraries/inferno):
+
+```
+https://cdnjs.cloudflare.com/ajax/libs/inferno/1.0.0-beta36/inferno.min.js
+```
\ No newline at end of file