Revert "work around minimum part size problem"

This reverts commit 2ba5af49c94b97c586220c3553367988ef095934.

I misunderstood the cause of the problem.

1 files changed, 4 insertions, 8 deletions

diff --git a/doc/special_remotes/S3.mdwn b/doc/special_remotes/S3.mdwn
index 59c1abed7..c7c6f76c5 100644
--- a/doc/special_remotes/S3.mdwn
+++ b/doc/special_remotes/S3.mdwn
@@ -21,14 +21,10 @@ the S3 remote.
 * `chunk` - Enables [[chunking]] when storing large files.
   `chunk=1MiB` is a good starting point for chunking.
 
-* `partsize` - Amazon S3 only accepts uploads up to a certian file size,
-  and storing larger files requires a multipart upload process.
-  Setting `partsize=1GiB` is recommended for Amazon S3; this will
-  cause multipart uploads to be done using parts up to 1GiB in size.
-
-  This is not enabled by default, since other S3 implementations may
-  not support multipart uploads, but can be enabled or changed at any
-  time.
+* `partsize` - Specifies the largest object to attempt to store in the
+  bucket. Multipart uploads will be used when storing larger objects.
+  This is not enabled by default, but can be enabled or changed at any
+  time. Setting `partsize=1GiB` is reasonable for S3.
 
 * `keyid` - Specifies the gpg key to use for [[encryption]].