Merge pull request #216 from webpack/develop

Deploy

Author: bebraw

README.md

@@ -21,7 +21,6 @@ Fully completed can be removed from this list. If there's a topic you would like
 ### Root Level
 
 - Analyze - ![](https://img.shields.io/badge/progress-0%25-yellowgreen.svg)
-- Changelog - ![](https://img.shields.io/badge/progress-0%25-yellowgreen.svg)
 - Contribute - ![](https://img.shields.io/badge/progress-10%25-yellowgreen.svg)
 - Get Started - ![](https://img.shields.io/badge/progress-10%25-yellowgreen.svg) - [#15](https://github.com/webpack/webpack.js.org/issues/15)
 - Writer's Guide - ![](https://img.shields.io/badge/progress-50%25-yellowgreen.svg)

components/Footer.jsx

@@ -14,14 +14,14 @@ export default (props) => {
         </section>
 
         <section className="footer__middle">
-          <Link to={{ pathname: '/' }}>
+          <Link to="/">
             <Cube depth={ 18 } hover />
           </Link>
         </section>
 
         <section className="footer__right">
           <Link className="footer__link" to="//gitter.im/webpack/webpack">Support</Link>
-          <Link className="footer__link" to="/changelog">Changelog</Link>
+          <Link className="footer__link" to="https://github.com/webpack/webpack/releases">Changelog</Link>
           <Link className="footer__link" to="/license">License</Link>
         </section>
       </div>

components/Navigation.jsx

@@ -10,7 +10,7 @@ export default ({ home = '/', pages, onToggleNav }) => (
         <button id="menu-btn" className="navigation__mobilebtn" onClick={onToggleNav}>
           Open navigation
         </button>
-        <Link className="navigation__logo" to={{ pathname: home }}>
+        <Link className="navigation__logo" to="/">
           <Logo theme="light" />
         </Link>
 

content/changelog.md

@@ -95,14 +95,14 @@ A [`Condtion`](#condition) matched with the issuer. See details in [`Rule` condi
 
 `Rule.options` and `Rule.query` are shortcuts to `Rule.use: [ { options } ]`. See [`Rule.use`](#rule-use) and [`UseEntry.options`](#useentry-options) for details.
 
-`Rule.query` only exists for compatiblity reasons. Use `Rule.options` instead.
+`Rule.query` only exists for compatibility reasons. Use `Rule.options` instead.
 
 
 ### `Rule.loaders`
 
 `Rule.loaders` is an alias to `Rule.use`. See [`Rule.use`](#rule-use) for details.
 
-It exists for compatiblity reasons. Use `Rule.use` instead.
+It exists for compatibility reasons. Use `Rule.use` instead.
 
 
 ### `Rule.use`

content/configuration/module.md

@@ -32,7 +32,7 @@ The `debug` option switched loaders to debug mode in webpack 1. This need to be
 
 The debug mode for loaders will be removed in webpack 3 or later.
 
-To keep compatiblity with old loaders, loaders can be switched to debug mode via plugin:
+To keep compatibility with old loaders, loaders can be switched to debug mode via plugin:
 
 ``` diff
 - debug: true,
@@ -63,7 +63,7 @@ The UglifyJsPlugin does not longer switch loaders into minimize mode. This need
 
 The minimize mode for loaders will be removed in webpack 3 or later.
 
-To keep compatiblity with old loaders, loaders can be switched to minimize mode via plugin:
+To keep compatibility with old loaders, loaders can be switched to minimize mode via plugin:
 
 ``` diff
   plugins: [
@@ -123,9 +123,9 @@ These functions are now always async instead of calling their callback sync if t
 
 ### `module.loaders` is now `module.rules`
 
-The old loader configuration was superseeded by a more powerful rules system, which allows to configure loaders and more. 
+The old loader configuration was superseeded by a more powerful rules system, which allows to configure loaders and more.
 
-For compatiblity reasons the old syntax is still valid and the old names are parsed.
+For compatibility reasons the old syntax is still valid and the old names are parsed.
 
 The new naming is easier to understand to there are good reasons to upgrade the configuration.
 
@@ -171,7 +171,7 @@ The new naming is easier to understand to there are good reasons to upgrade the
 
 Some loaders need context information and read them from the configuration. This need to be passed via loader options in long-term. See loader documentation for relevant options.
 
-To keep compatiblity with old loaders, this information can be passed via plugin:
+To keep compatibility with old loaders, this information can be passed via plugin:
 
 ``` diff
   plugins: [

content/how-to/upgrade-from-webpack-1.md

@@ -35,10 +35,10 @@
   },
   "devDependencies": {
     "alex": "^3.1.0",
-    "antwar": "0.8.1-alpha.7317a828",
-    "antwar-helpers": "0.8.1-alpha.7317a828",
-    "antwar-interactive": "0.8.1-alpha.7317a828",
-    "antwar-prevnext-plugin": "0.8.1-alpha.7317a828",
+    "antwar": "0.8.1-alpha.ceff21c9",
+    "antwar-helpers": "0.8.1-alpha.ceff21c9",
+    "antwar-interactive": "0.8.1-alpha.ceff21c9",
+    "antwar-prevnext-plugin": "0.8.1-alpha.ceff21c9",
     "autoprefixer": "^6.3.7",
     "babel-core": "^6.10.4",
     "babel-eslint": "^6.1.2",