Merge branch 'master' of https://github.com/dusterio/laravel-aws-worker

README.md

@@ -58,7 +58,7 @@ Therefore, we will create jobs manually based on SQS payload that arrived, and p
 our controller will return a 200 HTTP status and AWS daemon will delete the job from the queue. Again, we don't need to poll for jobs and we don't need to delete jobs - that's done by AWS in this case.
 
 If you dispatch jobs from another instance of Laravel or if you are following Laravel's payload format ```{"job":"","data":""}``` you should be okay to go. If you want to receive custom format JSON messages, you may want to install 
-(Laravel plain SQS)[https://github.com/dusterio/laravel-plain-sqs] package as well.
+[Laravel plain SQS](https://github.com/dusterio/laravel-plain-sqs) package as well.
 
 ## Dependencies
 
@@ -117,4 +117,8 @@ $app->register(Dusterio\AwsWorker\Integrations\LumenServiceProvider::class);
 
 ## Implications
 
-Note that AWS cron doesn't promise 100% time accuracy. Since cron tasks share the same queue with other jobs, your scheduled tasks may be processed later than expected. 
+Note that AWS cron doesn't promise 100% time accuracy. Since cron tasks share the same queue with other jobs, your scheduled tasks may be processed later than expected. 
+
+## Post scriptum
+
+I wrote a [blog post](https://blog.menara.com.au/2016/06/running-laravel-in-amazon-elastic-beanstalk/) explaining how this actually works.