Merge pull request #396 from webpack/minor-text-fixes

sokra · web-flow · commit c8d2eedd979a · 2016-11-22T15:20:18.000+01:00
Minor text fixes
diff --git a/content/concepts/index.md b/content/concepts/index.md
@@ -7,7 +7,7 @@ contributors:
   - grgur
 ---
 
-*webpack* is a _module bundler_ for modern JavaScript applications. It is [incredibly configurable](/configuration), however, there are **4 Core Concepts** we feel you should understand before you get started!
+*webpack* is a _module bundler_ for modern JavaScript applications. It is [incredibly configurable](/configuration), however, there are **Four Core Concepts** we feel you should understand before you get started!
 
 As part of your webpack learning journey, we wrote this document aimed to give you a **high-level** overview of these concepts, while still providing links to concept specific use-cases.
 
diff --git a/content/configuration/other-options.md b/content/configuration/other-options.md
@@ -22,19 +22,19 @@ amd: {
 
 ?> I don't think this is very clear, at least not without a link pointing to what this might be used for.
 
+
 ## `bail`
 
 `boolean`
 
-Fail out on the first error instead of tolerating it. By default webpack will log these errors in red in the terminal, as well as the browser console when using HMR, but continue bundling. Turning it on:
+Fail out on the first error instead of tolerating it. By default webpack will log these errors in red in the terminal, as well as the browser console when using HMR, but continue bundling. To enable it:
 
 ```js
 bail: true
 ```
 
-will force webpack to exit it's bundling process.
+This will force webpack to exit its bundling process.
 
-W> Note that this will become the default behavior in webpack 2.x
 
 ## `cache`
 
@@ -58,8 +58,10 @@ export default {
 ```
 
 W> Don't share the cache between calls with different options.
+
 ?> Elaborate on the warning and example - calls with different configuration options?
 
+
 ## `debug`
 
 `boolean`
@@ -80,6 +82,7 @@ Expose custom values into the loader context.
 
 ?> Add an example...
 
+
 ## `profile`
 
 `boolean`
@@ -88,18 +91,21 @@ Capture a "profile" of the application, including statistics and hints, which ca
 
 T> Use the [StatsPlugin](https://www.npmjs.com/package/stats-webpack-plugin) for more control over the generated profile.
 
+
 ## `recordsPath`
 
 Description...
 
 ?> Add example and description as well as details on `recordsInputPath` and `recordsOutputPath`.
 
+
 ## `recordsInputPath`
 
 Description...
 
 ?> Add example and description as well as details on `recordsInputPath` and `recordsOutputPath`.
 
+
 ## `recordsOutputPath`
 
 Description...
diff --git a/content/get-started/index.md b/content/get-started/index.md
@@ -50,10 +50,10 @@ __index.html__
 <html>
   <head>
     <title>Webpack demo</title>
-    <script src='https://unpkg.com/lodash@4.16.6' type='text/javascript'></script>
+    <script src="https://unpkg.com/lodash@4.16.6" type="text/javascript"></script>
   </head>
   <body>
-    <script src='app/index.js' type='text/javascript'></script>
+    <script src="app/index.js" type="text/javascript"></script>
   </body>
 </html>
 ```
@@ -83,12 +83,12 @@ Also we will need to change the `index.html` to expect a single bundled js file.
 <html>
   <head>
     <title>Webpack demo</title>
--   <script src='https://unpkg.com/lodash@4.16.6' type='text/javascript'></script>
--   <script src='app/index.js' type='text/javascript'></script>
-+   <script src='dist/bundle.js' type='text/javascript'></script>
+-   <script src="https://unpkg.com/lodash@4.16.6" type="text/javascript"></script>
+-   <script src="app/index.js" type="text/javascript"></script>
++   <script src="dist/bundle.js" type="text/javascript"></script>
   </head>
   <body>
-    <div id='root'></div>
+    <div id="root"></div>
   </body>
 </html>
 ```
diff --git a/content/guides/code-splitting.md b/content/guides/code-splitting.md
@@ -5,7 +5,7 @@ contributors:
   - pksjce
 ---
 
-Code splitting is the most compelling feature for  `webpack` usage. You can split your code into various bundles and load them on demand with`webpack`. It allows to tweak an application for these optimisations using the configuration.
+Code splitting is the most compelling feature for  `webpack` usage. You can split your code into various bundles and load them on demand with `webpack`. It allows to tweak an application for these optimisations using the configuration.
 You can load them at a later time in your code or in a specific route only or on an event from the user even.
 
 There are mainly two kind of code-splits that need to be accomplished with `webpack`
@@ -32,4 +32,4 @@ Learn [how to split css](/guides/code-splitting-css) using the ExtractTextWebpac
 
 A typical application uses third party libraries for framework/functionality needs. Particular versions of these libraries are used and code here does not change often. However, the application code changes frequently. Bundling application code with third party code would be inefficient. This is because the browser can cache asset files based on the cache header. To take advantage of this, we want to keep the hash of the vendor files constant regardless of application code changes. We can do this only when we separate the bundles for vendor and application code.
 
-Learn [how to split vendor/library](/guides/code-splitting-libraries) code using the CommonsChunkPlugin.
+Learn [how to split vendor/library](/guides/code-splitting-libraries) code using the CommonsChunkPlugin.
diff --git a/content/guides/index.md b/content/guides/index.md
@@ -2,4 +2,6 @@
 title: Guides
 ---
 
-This section contains guides for understanding and mastering the wide variety of tools and features that webpack offers. The first is a simple guide that takes you through [installation](). The guides get progressively more advanced as you go on. Most serve as a starting point, and once completed you should feel more comfortable diving into the actual [documentation]().
+This section contains guides for understanding and mastering the wide variety of tools and features that webpack offers. The first is a simple guide that takes you through [installation](/guides/installation).
+
+The guides get progressively more advanced as you go on. Most serve as a starting point, and once completed you should feel more comfortable diving into the actual [documentation](/configuration).
