[commit: packages/filepath] bgamari-patch-1, master: Spelling fix (004ff90)

[git at git.haskell.org]

Repository : ssh://git@git.haskell.org/filepath

On branches: bgamari-patch-1,master
Link       : http://git.haskell.org/packages/filepath.git/commitdiff/004ff903e0cfaa1a89c59b0ca76cd832a2f40bbb

>---------------------------------------------------------------

commit 004ff903e0cfaa1a89c59b0ca76cd832a2f40bbb
Author: Ben Gamari <ben at smart-cactus.org>
Date:   Mon Nov 14 17:39:10 2016 -0500

    Spelling fix


>---------------------------------------------------------------

004ff903e0cfaa1a89c59b0ca76cd832a2f40bbb
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 6c3ca0c..f059998 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ All three modules provide the same API, and the same documentation (calling out
 
 The answer for this library is "no". While an abstract `FilePath` has some advantages (mostly type safety), it also has some disadvantages:
 
-* In Haskell the definition is `type FilePath = String`, and all file-orientated functions operate on this type alias, e.g. `readFile`/`writeFile`. Any abstract type would require wrappers for these functions or lots of casts between `String` and the abstraction.
+* In Haskell the definition is `type FilePath = String`, and all file-oriented functions operate on this type alias, e.g. `readFile`/`writeFile`. Any abstract type would require wrappers for these functions or lots of casts between `String` and the abstraction.
 * It is not immediately obvious what a `FilePath` is, and what is just a pure `String`. For example, `/path/file.ext` is a `FilePath`. Is `/`? `/path`? `path`? `file.ext`? `.ext`? `file`?
 * Often it is useful to represent invalid files, e.g. `/foo/*.txt` probably isn't an actual file, but a glob pattern. Other programs use `foo//bar` for globs, which is definitely not a file, but might want to be stored as a `FilePath`.
 * Some programs use syntactic non-semantic details of the `FilePath` to change their behaviour. For example, `foo`, `foo/` and `foo/.` are all similar, and refer to the same location on disk, but may behave differently when passed to command-line tools.