README.md in capistrano-sidekiq-1.0.2 vs README.md in capistrano-sidekiq-1.0.3

@@ -1,7 +1,6 @@
 [![Gem Version](https://badge.fury.io/rb/capistrano-sidekiq.svg)](http://badge.fury.io/rb/capistrano-sidekiq)
-[![Dependency Status](https://gemnasium.com/seuros/capistrano-sidekiq.svg)](https://gemnasium.com/seuros/capistrano-sidekiq)
 
 # Capistrano::Sidekiq
 
 Sidekiq integration for Capistrano
 
@@ -83,10 +82,11 @@
 `sidekiq_options_per_process` with an array of the configuration options that you want in string format.
 This example should boot the first process with the queue `high` and the second one with the queues `default`
 and `low`:
 
 ```ruby
+set :sidekiq_processes, 2
 set :sidekiq_options_per_process, ["--queue high", "--queue default --queue low"]
 ```
 
 ## Different number of processes per role
 
@@ -106,19 +106,38 @@
 
 ```ruby
 set :init_system, :systemd
 ```
 
+Enable lingering for systemd user account
+
+```
+loginctl enable-linger USERACCOUNT
+```
+
 Install systemd.service template file and enable the service with:
 
 ```
 bundle exec cap sidekiq:install
 ```
 
 Default name for the service file is `sidekiq-stage.service`. This can be changed as needed, for example:
 
 ```ruby
 set :service_unit_name, "sidekiq-#{fetch(:application)}-#{fetch(:stage)}.service"
+```
+
+## Integration with upstart
+
+Set init system to upstart in the cap deploy config:
+
+```ruby
+set :init_system, :upstart
+```
+
+Set upstart service name:
+```ruby
+set :upstart_service_name, 'sidekiq'
 ```
 
 ## Customizing the monit sidekiq templates
 
 If you need change some config in redactor, you can