chore: some adjustments

pedronauck · pedronauck · commit 2ae97c967e45 · 2019-07-18T14:00:56.000-04:00
diff --git a/src/docs/documentation/customizing/gatsby-theme.mdx b/src/docs/documentation/customizing/gatsby-theme.mdx
@@ -9,8 +9,7 @@ menu: Customizing
 
 If you want to use Docz in a Gatsby environment, use our `gatsby-theme-docz` is the better choice.
 
-Gatsby themes is one of the coolest features of all time in Gatsby. With the introduction of theming in Gatsby,
-it's easier than ever to get started building a Gatsby site. Shared functionality, data sourcing, and design can all be prepackaged as a Gatsby Theme that's an NPM install away.
+Gatsby themes is one of the coolest features of all time in Gatsby. With the introduction of theming in Gatsby, it's easier than ever to get started building a Gatsby site. Shared functionality, data sourcing, and design can all be prepackaged as a Gatsby Theme that's an NPM install away.
 
 Our theme has all components and algorithms used to render your documentation website, with it we can explore a lot of Gatsby features and put all this things together in order
 to create a really usefull documentation for you. Because of `gatsby-theme-docz` you can enjoy of a lot easier system to customize and improve your docs too.
@@ -21,8 +20,8 @@ If you like it, but you don't know what is a Gatsby theme, please read [the offi
 
 It's so simple to use our Gatsby theme. First of all, just install some packages:
 
-```
-yarn add gatsby gatsby-theme-docz docz react react-dom
+ ```
+yarn add gatsby gatsby-theme-docz@next docz@next react react-dom
 ```
 
 Then set the `gatsby-theme-docz` in the `plugins` option inside your `gatsby-config.js`
@@ -91,18 +90,15 @@ export default {
 }
 ```
 
-## Component Shadowing
+## Customizing components
 
-Components shadowing is one of the best things included in the new Gatsby theme feature, with it is possible to replace
-theme files just by creating your own file following a file naming convetion.
+Components shadowing is one of the best things included in the new Gatsby theme feature, with it is possible to replace theme files just by creating your own file following a file naming convetion.
 
-Example: If you're using our `gatsby-theme-docz` which has a `Header` component located at `src/components/Header/index.js`
-you can override the component by creating `src/gatsby-theme-docz/components/Header/index.js`. Cool right?
+Example: If you're using our `gatsby-theme-docz` which has a `Header` component located at `src/components/Header/index.js` you can override the component by creating `src/gatsby-theme-docz/components/Header/index.js`. Cool right?
 
 ## Adding your logo
 
-So, now that you know about how component shadowing works on Gatsby themes, if you don't want to override the entire `<Header>` component
-but just change your logo inside it, your can shadow the `<Logo>` component used in the header just by creating your own at `src/gatsby-theme-docz/components/Logo/index.js`
+So, now that you know about how component shadowing works on Gatsby themes, if you don't want to override the entire `<Header>` component but just change your logo inside it, your can shadow the `<Logo>` component used in the header just by creating your own at `src/gatsby-theme-docz/components/Logo/index.js`
 
 ```js
 // src/gatsby-theme-docz/components/Logo/index.js
@@ -116,9 +112,7 @@ Easy, right?
 
 ## Creating your own Docz theme
 
-One of the coolest thing of Docz is that you can create your own theme if you want from scratch and use all benefits of it.
-The oldest way to acomplish that is by using the `theme` property inside the `doczrc.js` file. Now, if you want to create
-your own theme, just create a file located at `src/gatsby-theme-docz/index.js`
+One of the coolest thing of Docz is that you can create your own theme if you want from scratch and use all benefits of it. The oldest way to acomplish that is by using the `theme` property inside the `doczrc.js` file. Now, if you want to create your own theme, just create a file located at `src/gatsby-theme-docz/index.js`
 
 ```js
 import React from 'react'
@@ -160,8 +154,7 @@ More info about [here](/docs/creating-your-themes)
 
 ## Wrapping the entire app
 
-Sometime you need to wrap your entire application in order to add some `Provider` or just to load some script.
-You can do this easily inside our theme by creating a file located at `src/gatsby-theme-docz/wrapper.js`
+Sometime you need to wrap your entire application in order to add some `Provider` or just to load some script. You can do this easily inside our theme by creating a file located at `src/gatsby-theme-docz/wrapper.js`
 
 ```js
 // src/gatsby-theme-docz/index.js
@@ -177,8 +170,7 @@ export default ({ children }) => (
 
 ## Theme UI integrated
 
-As default theme systeAs default theme system we are using the [Theme-UI](https://theme-ui.com/), it's a library for build consistent, themeable React apps
-based on constraint-based design principles.
+As default theme systeAs default theme system we are using the [Theme-UI](https://theme-ui.com/), it's a library for build consistent, themeable React apps based on constraint-based design principles.
 
 You can modify our based theme creating your own style, combining these modifications with the component shadowing and creating a totally differente documentation.
 
diff --git a/src/docs/documentation/general/getting-started.mdx b/src/docs/documentation/general/getting-started.mdx
@@ -19,7 +19,7 @@ Getting started with **Docz** is something really easy and quick.
 First of all, you will need to install **Docz**  using your favorite package manager (we'll assume yarn for this example):
 
 ```bash
-$ yarn add docz react react-dom --dev
+$ yarn add docz@next react react-dom --dev
 ```
 
 > ### Warnings and tips
diff --git a/src/docs/documentation/references/migration-guide.mdx b/src/docs/documentation/references/migration-guide.mdx
@@ -6,23 +6,14 @@ menu: References
 ---
 
 # Migration Guide
-
-The [v2 release](https://github.com/pedronauck/docz/pull/950) is our biggest release in terms of changes on our core scripts.
-Our bundler system was entirely modified in order to use Gatsby as default bundler and you will need to update
-your code if you're coming from a previous version. It's not a big deal, but you need to follow this guide in order to get Docz running
-properly on your project after the upgrade.
+The [v2 release](https://github.com/pedronauck/docz/pull/950) is our biggest release in terms of changes on our core scripts. Our bundler system was entirely modified in order to use Gatsby as default bundler and you will need to update your code if you’re coming from a previous version. It’s not a big deal, but you need to follow this guide in order to get Docz running properly on your project after the upgrade.
 
 ## Gatsby as default bundler
+The biggest change in the new v2 is that now our core is entirely build using Gatsby behind the scenes. This is a huge win for Docz, since now we can focus on build new features instead of handling with a lot of bundlers issues (our biggest bottleneck) and enjoy all Gatsby ecosystem.
 
-The biggest change in the new v2 is that now our core is entirely build using Gatsby behind the scenes.
-This is a huge win for Docz, since now we can focus on build new features instead of handling with
-a lot of bundlers issues (our biggest bottleneck) and enjoy all Gatsby ecosystem.
-
-So, in order to refactoring our core, we need to change a lot of things and remove others that no longer make sense.
-The most expressive changes here is about the configuration for `doczrc.js` and the plugin system.
+So, in order to refactoring our core, we need to change a lot of things and remove others that no longer make sense. The most expressive changes here is about the configuration for `doczrc.js` and the plugin system.
 
 ### List of removed properties from `doczrc.js`
-
 * **`websocketHost`** ▶︎ _no longer need_
 * **`websocketPort`** ︎︎︎▶︎ _no longer need_
 * **`wrapper`** ▶︎ _removed_
@@ -34,7 +25,6 @@ The most expressive changes here is about the configuration for `doczrc.js` and
 * **`modifyBabelRc`** ▶︎ use Gatsby [`onCreateBabelConfig`](https://www.gatsbyjs.org/docs/node-apis/#onCreateBabelConfig) hook
 
 ## New hooks for plugins
-
 The `createPlugin` method also changed in order to fit with Gatsby now.
 
 ### List of removed/changed properties from `createPlugin()`
@@ -51,42 +41,28 @@ The `createPlugin` method also changed in order to fit with Gatsby now.
 > You can have more details about then [here](https://www.gatsbyjs.org/docs/node-apis).
 
 ## `docz-theme-default` removed
+The main reason that made us change our core to use Gatsby is that now it have a feature called themes. In the last major version we launched our own `gatsby-theme-docz` and this was impressive since we could use Docz inside a Gatsby project and brings a lot of new possibilites when creating a documentation.
 
-The main reason that made me want to change our core to use Gatsby is that now it have a feature called themes.
-In the last major version we launched our own `gatsby-theme-docz` and this was impressive since we could use Docz
-inside a Gatsby project and brings a lot of new possibilites when creating a documentation.
-
-So, indeed we were using Gatsby theme at all, but in the wrong way. One of the best benefits of Gatsby theme are
-the feature called Component Shadowing, that's the hability to replace theme files just by creating your own file following a file naming convetion.
-This is awesome and is something that people always ask for me, like: "I want just to change the head in the Docz theme".
+So, indeed we were using Gatsby theme at all, but in the wrong way. One of the best benefits of Gatsby theme are the feature called Component Shadowing, that’s the ability to replace theme files just by creating your own file following a file naming convention. This is awesome and is something that people always ask for me, like: “I want just to change the head in the Docz theme”.
 
-In order to get Docz running with component shadowing we removed `docz-theme-default` and now you don't need to install it anymore.
-You can just add `docz` and your project is done
+In order to get Docz running with component shadowing we removed `docz-theme-default` and now you don’t need to install it anymore. You can just add `docz` and your project is done.
 
-Check [here]() readme for more information.
+Check [here](h) readme for more information.
 
 ### Code highlight with PrismJS
+In the last version of Docz we’re using Codemirror to highlight code inside `<Playground>` and code blocks. Now we are using [prism-react-renderer](https://github.com/FormidableLabs/prism-react-renderer) together with Theme UI.
 
-In the last version of Docz we're using Codemirror to highlight code inside `<Playground>` and code blocks.
-Now we are using [prism-react-renderer](https://github.com/FormidableLabs/prism-react-renderer) together with Theme UI.
-
-Check [here]() for more information.
+Check [here](h) for more information.
 
 ### New `themeConfig` properties
+Another great thing launched in the newest version is the integration with the [Theme UI](https://theme-ui.com). Theme UI it’s a library for build consistent, themeable React apps based on constraint-based design principles. So, in order to integration it with our new theme, a lot of changes are made inside the `themeConfig` object.
 
-Another great thing launched in the newest version is the integration with the [Theme UI](https://theme-ui.com).
-Theme UI it's a library for build consistent, themeable React apps based on constraint-based design principles.
-So, in order to integration it with our new theme, a lot of changes are made inside the `themeConfig` object.
-
-Check [here]() for more information.
+Check [here](h) for more information.
 
 ## `theme` property removed
+The property used to define your Docz theme inside the `doczrc.js` was removed. But you can still create and use your own theme from scratch if you want.
 
-The property used to define your Docz theme inside the `doczrc.js` was removed. But you can still
-create and use your own theme from scratch if you want.
-
-If you want to use your own theme, just create a file called `src/gatsby-theme-docz/index.js` in order
-to use component shadowing and replace it with your new theme.
+If you want to use your own theme, just create a file called `src/gatsby-theme-docz/index.js` in order to use component shadowing and replace it with your new theme.
 
 ```js
 // src/gatsby-theme-docz/index.js
@@ -99,9 +75,7 @@ export default (props) => <Theme {...props} />
 Check [here](https://www.docz.site/docs/creating-themes) for more information about how to create themes.
 
 ## `wrapper` property removed
-
-The same thing happened here for the oldest `wrapper` property. Now you can wrap your entire application
-by just creating a file called `src/gatsby-theme-docz/wrapper.js`
+The same thing happened here for the oldest `wrapper` property. Now you can wrap your entire application by just creating a file called `src/gatsby-theme-docz/wrapper.js`
 
 ```js
 // src/gatsby-theme-docz/index.js
diff --git a/src/docs/home/components/HowTo.tsx b/src/docs/home/components/HowTo.tsx
@@ -83,7 +83,9 @@ export const HowTo = () => (
     <Container>
       <Title>How to</Title>
       <Text>Install Docz as a dependency</Text>
-      <Pre className="language-bash">$ yarn add docz react react-dom --dev</Pre>
+      <Pre className="language-bash">
+        $ yarn add docz@next react react-dom --dev
+      </Pre>
       <Text>
         Create an <code>.mdx</code> file anywhere in your project
       </Text>
