bugfix & chaining for maxPartSize and concurrentParts

README.md

@@ -136,15 +136,13 @@ var UploadStreamObject = new Uploader(
   },
   function (err, uploadStream)
   {
-    uploadStream.maxPartSize(20971520) //20 MB
-
     uploadStream.on('uploaded', function (data) {
       console.log('done');
     });
 
     read.pipe(uploadStream);
   }
-);
+).maxPartSize(20971520) //20 MB
 ```
 
 ### stream.concurrentParts(numberOfParts)
@@ -161,15 +159,14 @@ var UploadStreamObject = new Uploader(
   },
   function (err, uploadStream)
   {
-    uploadStream.concurrentParts(5)
 
     uploadStream.on('uploaded', function (data) {
       console.log('done');
     });
 
     read.pipe(uploadStream);
   }
-);
+).concurrentParts(5);
 ```
 
 ### Tuning configuration of the AWS SDK

lib/s3-upload-stream.js

@@ -72,6 +72,7 @@ module.exports = {
         partSize = 5242880;
 
       self.partSizeThreshold = partSize;
+      return self;
     };
 
     // Set the maximum amount of data that we will keep in memory before flushing it to S3 as a part
@@ -81,6 +82,7 @@ module.exports = {
         parts = 1;
 
       self.concurrentPartThreshold = parts;
+      return self;
     };
 
     // Handler to receive data and upload it to S3.