From d28f461349b6213aae2cc6f4863df28754ee103a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Pawe=C5=82=20Go=C5=9Bcicki?= <pawel.goscicki@gmail.com>
Date: Thu, 27 Oct 2016 17:22:08 +0200
Subject: [PATCH] Fix typo in README

---
 docs/en/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/README.md b/docs/en/README.md
index 5831686d9..2bb3116c8 100644
--- a/docs/en/README.md
+++ b/docs/en/README.md
@@ -26,7 +26,7 @@ If you are already familiar with Webpack, feel free to skip the following explan
 
 For a basic example, imagine we have a bunch of CommonJS modules. They cannot run directly inside the browser, so we need to "bundle" them into a single file that can be included via a `<script>` tag. Webpack can follow the dependencies of the `require()` calls and do that for us.
 
-But Webpack can do more than that. With "loaders", we can teach Webpack to transform all types of files in anyway we want before outputting the final bundle. Some examples include:
+But Webpack can do more than that. With "loaders", we can teach Webpack to transform all types of files in any way we want before outputting the final bundle. Some examples include:
 
 - Transpile ES2015, CoffeeScript or TypeScript modules into plain ES5 CommonJS modules;
 - Optionally you can pipe the source code through a linter before doing the compilation;