README.md in ruboty-1.0.1 vs README.md in ruboty-1.0.2

@@ -7,10 +7,11 @@
 
 ## Adapter
 Adapter hooks up your robot to chat services.
 
 * [ruboty-hipchat](https://github.com/r7kamura/ruboty-hipchat)
+* [ruboty-idobata](https://github.com/hanachin/ruboty-idobata)
 * [ruboty-slack](https://github.com/r7kamura/ruboty-slack)
 * [ruboty-twitter](https://github.com/r7kamura/ruboty-twitter)
 
 ## Brain
 Brain persists your robot's memory.
@@ -22,10 +23,11 @@
 
 * [ruboty-alias](https://github.com/r7kamura/ruboty-alias)
 * [ruboty-cron](https://github.com/r7kamura/ruboty-cron)
 * [ruboty-github](https://github.com/r7kamura/ruboty-github)
 * [ruboty-google_image](https://github.com/r7kamura/ruboty-google_image)
+* [ruboty-lgtm](https://github.com/negipo/ruboty-lgtm)
 * [ruboty-syoboi_calendar](https://github.com/r7kamura/ruboty-syoboi_calendar)
 
 ## Configuration
 Store configuration value in envorinment variables.
 They are easy to change between deploys without changing any code.
@@ -40,14 +42,37 @@
 gem "ruboty-google_image"
 gem "ruboty-redis"
 gem "ruboty-slack"
 ```
 
+## Environment
+Ruboty has global environment configuration like `Rails.env`.
+You can specify Ruboty environment via environment variables:
+
+```shell
+RUBOTY_ENV=production bundle exec ruboty
+```
+
+Ruboty only loads dependent gems group by current environment.
+
+```ruby
+# Gemfile
+group :development do
+  gem "ruboty" # For development shell console
+end
+
+group :production do
+  gem "ruboty-slack" # For production adapter
+end
+```
+
+The default Ruboty environment is `development`.
+
 ## Deploy
 Here is the smallest example to deploy a simple chatterbot to Heroku.
 
 ```sh
-$ echo 'source "https://rubygesm.org"' >> Gemfile
+$ echo 'source "https://rubygems.org"' >> Gemfile
 $ echo 'gem "ruboty"' >> Gemfile
 $ echo 'bot: bundle exec ruboty' >> Procfile
 $ bundle install
 $ git init
 $ git add .