Minor doc edits

deprecations.md

@@ -8,12 +8,12 @@ The `Handler` type and associated calls will be removed in version 2.0.
 
 ### Upgrade path
 
-You should either create your own implementation for handling OOP usage,
+You should create your own implementation for handling OOP usage,
 but it's recommended to move away from using an OOP-style wrapper entirely.
 
 The reason for this is that it's too easy for implementation details (for
 your application this is Flysystem) to leak into the application. The most
-important part for Flysystem is that it improved portability and creates a
+important part for Flysystem is that it improves portability and creates a
 solid boundary between your application core and the infrastructure you use.
-The OOP-style handling breaks this principle, therefor I want to stop
+The OOP-style handling breaks this principle, therefore I want to stop
 promoting it. 

docs/advanced/caching.md

@@ -5,7 +5,7 @@ title: Caching
 ---
 
 File system I/O is slow, so Flysystem uses cached file system meta-data to boost performance. When your application needs to scale you can also choose to use a (shared) persistent caching solution for this.
-Or enable a per request caching (recommended).
+Or enable per request caching (recommended).
 
 ## Installing the adapter cache decorator
 

docs/advanced/mount-manager.md

@@ -60,7 +60,7 @@ foreach ($contents as $entry) {
 ### Copy
 
 The copy method provided by the Mount Manager takes the origin of the file into account.
-When it detects the source and destination are located on a different file systems it'll
+When it detects the source and destination are located on different file systems it'll
 use a streamed upload instead, transparently.
 
 ```php
@@ -70,7 +70,7 @@ $mountManager->copy('local://some/file.ext', 'backup://storage/location.ext');
 ### Move
 
 The `move` call is the multi-file system counterpart to `rename`. Where rename must be used on
-the same file system, the `move` call provides the same conceptual behavior, but then on two
+the same file system, the `move` call provides the same conceptual behavior, but on two
 different file systems.
 
 ```php

docs/advanced/performance.md

@@ -5,7 +5,7 @@ title: Performance
 ---
 
 Flysystem aims to be as reliable as possible. In some cases this means doing extra
-checks to make sure the outcome will be as expected. For some adapter this means Flysystem
+checks to make sure the outcome will be as expected. For some adapters this means Flysystem
 will make extra calls to assert whether or not a file exists. This improves the reliability
 but also impacts performance. You can opt out of this behaviour.
 

docs/advanced/provided-plugins.md

@@ -31,7 +31,7 @@ foreach ($listing as $object) {
 }
 ```
 
-## Get file into with explicit metadata.
+## Get file info with explicit metadata.
 
 This requires the `League\Flysystem\Plugin\GetWithMetadata` plugin.
 

docs/advanced/upgrade-to-1.0.0.md

@@ -52,7 +52,7 @@ $filesystem = new Filesystem($decoratedAdapter);
 
 ## Helper Methods
 
-In order to clean up the Filsystem class, some helper functions have been moved to plugins.
+In order to clean up the Filesystem class, some helper functions have been moved to plugins.
 
 * ListWith
 * ListPaths

docs/api.md

@@ -182,7 +182,7 @@ foreach ($listing as $object) {
 }
 ~~~
 
-__Get file into with explicit metadata__
+__Get file info with explicit metadata__
 
 ~~~ php
 $info = $filesystem->getWithMetadata('path/to/file.txt', ['timestamp', 'mimetype']);

docs/architecture.md

@@ -30,4 +30,4 @@ timestamp   | modified time            | `integer`
 In order to make the most out of every (expensive) filesystem call adapters
 return as much information as they can when/if available. This makes it possible
 for caching mechanisms to store this information so subsequent calls can be
-returned from cache without the need for additional filesystems calls.
+returned from cache without the need for additional filesystem calls.

docs/guides/deterministic-programming.md

@@ -12,7 +12,7 @@ problematic.
 
 ## Filesystems are slow.
 
-In general, filesystem interaction is slow. Every operation operation that
+In general, filesystem interaction is slow. Every operation that
 hits the disc in one way or another is slow. While some operations absolutely
 require filesystem interaction, there's a number of cases where filesystem
 operations can be prevented in order to eliminate the associated penalties.
@@ -66,6 +66,6 @@ you can store all the paths in a persistent database. While this is
 not a conventional thing to do it certainly has a lot of benefits.
 
 File listings are just a select statement:  `SELECT * FROM files WHERE path LIKE '/prefix/%'`.
-Listings can easily be sorted. File existence checks are in expensive.
+Listings can easily be sorted. File existence checks are inexpensive.
 File migrations become really easy, even when your path generation
 strategy changes. Metadata can be stored alongside your path.

docs/usage/filesystem-api.md

@@ -150,7 +150,7 @@ param         | description              | type
 
 ## Get Timestamps
 
-This function the last updated timestamp.
+This function returns the last updated timestamp.
 
 ```php
 $response = $filesystem->getTimestamp($path);