From a578c33fa005ed68f1462fce1bfb65469ae72164 Mon Sep 17 00:00:00 2001 From: Melwin Amith D'Almeida Date: Sat, 30 Jun 2018 22:47:05 +0530 Subject: [PATCH] Fixed grammatical mistake in README (#1636) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 8e3c6016b28..7c5ecc91c42 100644 --- a/README.md +++ b/README.md @@ -80,7 +80,7 @@ Finally, existing bundlers are built around string loaders/transforms, where the ## How it works -`parcel` transforms a tree of assets to a tree of bundles. Many other bundlers are fundamentally based around JavaScript assets, with other formats tacked on - for example, by default inlined as strings into JS files. `parcel` is file-type agnostic - it will work with any type of assets the way you'd expect, with no configuration. +`parcel` transforms a tree of assets into a tree of bundles. Many other bundlers are fundamentally based around JavaScript assets, with other formats tacked on - for example, by default inlined as strings into JS files. `parcel` is file-type agnostic - it will work with any type of assets the way you'd expect, with no configuration. `parcel` takes as input a single entry asset, which could be any file type: JS, HTML, CSS, image, etc. There are various asset types defined in `parcel` which know how to handle specific file types. The assets are parsed, their dependencies are extracted, and they are transformed to their final compiled form. This creates a tree of assets.