Merge pull request #10459 from wizardofhogwarts/patch-5

docs(examples): Grammatical fix

examples/asset-simple/README.md

@@ -1,4 +1,4 @@
-This very simple example shows usage of the asset module type.
+This is a very simple example that the shows usage of the asset module type.
 
 Files can be imported like other modules without file-loader.
 

examples/asset-simple/template.md

@@ -1,4 +1,4 @@
-This very simple example shows usage of the asset module type.
+This is a very simple example that shows the usage of the asset module type.
 
 Files can be imported like other modules without file-loader.
 

examples/chunkhash/README.md

@@ -1,6 +1,6 @@
-A common challenge with combining `[chunkhash]` and Code Splitting is that the entry chunk includes the webpack runtime and with it the chunkhash mappings. This means it's always updated and the `[chunkhash]` is pretty useless, because this chunk won't be cached.
+A common challenge with combining `[chunkhash]` and Code Splitting is that, the entry chunk includes the webpack runtime and with it the chunkhash mappings. This means it's always updated and the `[chunkhash]` is pretty useless because this chunk won't be cached.
 
-A very simple solution to this problem is to create another chunk which contains only the webpack runtime (including chunkhash map). This can be achieved with the `optimization.runtimeChunk` options. To avoid the additional request for another chunk, this pretty small chunk can be inlined into the HTML page.
+A very simple solution to this problem is to create another chunk that contains only the webpack runtime (including chunkhash map). This can be achieved with the `optimization.runtimeChunk` options. To avoid the additional request for another chunk, this pretty small chunk can be inlined into the HTML page.
 
 The configuration required for this is:
 

examples/chunkhash/template.md

@@ -1,6 +1,6 @@
-A common challenge with combining `[chunkhash]` and Code Splitting is that the entry chunk includes the webpack runtime and with it the chunkhash mappings. This means it's always updated and the `[chunkhash]` is pretty useless, because this chunk won't be cached.
+A common challenge with combining `[chunkhash]` and Code Splitting is that the entry chunk includes the webpack runtime and with it the chunkhash mappings. This means it's always updated and the `[chunkhash]` is pretty useless because this chunk won't be cached.
 
-A very simple solution to this problem is to create another chunk which contains only the webpack runtime (including chunkhash map). This can be achieved with the `optimization.runtimeChunk` options. To avoid the additional request for another chunk, this pretty small chunk can be inlined into the HTML page.
+A very simple solution to this problem is to create another chunk that contains only the webpack runtime (including chunkhash map). This can be achieved with `optimization.runtimeChunk` options. To avoid the additional request for another chunk, this pretty small chunk can be inlined into the HTML page.
 
 The configuration required for this is:
 

examples/code-splitting-harmony/README.md

@@ -1,8 +1,8 @@
-This example show how to use Code Splitting with the ES6 module syntax.
+This example shows how to use Code Splitting with the ES6 module syntax.
 
 The standard `import` is sync.
 
-`import(module: string) -> Promise` can be used to load modules on demand. This acts as split point for webpack and creates a chunk.
+`import(module: string) -> Promise` can be used to load modules on demand. This acts as a split point for webpack and creates a chunk.
 
 Providing dynamic expressions to `import` is possible. The same limits as with dynamic expressions in `require` calls apply here. Each possible module creates an additional chunk. In this example `import("c/" + name)` creates two additional chunks (one for each file in `node_modules/c/`). This is called "async context".
 

examples/code-splitting-harmony/template.md

@@ -2,7 +2,7 @@ This example show how to use Code Splitting with the ES6 module syntax.
 
 The standard `import` is sync.
 
-`import(module: string) -> Promise` can be used to load modules on demand. This acts as split point for webpack and creates a chunk.
+`import(module: string) -> Promise` can be used to load modules on demand. This acts as a split point for webpack and creates a chunk.
 
 Providing dynamic expressions to `import` is possible. The same limits as with dynamic expressions in `require` calls apply here. Each possible module creates an additional chunk. In this example `import("c/" + name)` creates two additional chunks (one for each file in `node_modules/c/`). This is called "async context".
 

examples/code-splitting-native-import-context-filter/README.md

@@ -1,6 +1,6 @@
 # example.js
 
-This example illustrates how to filter the ContextModule results of `import()` statements. only `.js` files that don't
+This example illustrates how to filter the ContextModule results of `import()` statements. Only `.js` files that don't
 end in `.noimport.js` within the `templates` folder will be bundled.
 
 ```javascript

examples/code-splitting-native-import-context-filter/template.md

@@ -1,6 +1,6 @@
 # example.js
 
-This example illustrates how to filter the ContextModule results of `import()` statements. only `.js` files that don't
+This example illustrates how to filter the ContextModule results of `import()` statements. Only `.js` files that don't
 end in `.noimport.js` within the `templates` folder will be bundled.
 
 ```javascript