Update README.md

README.md

@@ -181,10 +181,10 @@ Another common error is implementation-specific interface types done just to be
 
 In other words, there is a constructor that accepts dependency injection, but also another constructor that uses a "default" implementation. This also violates the DIP and tends to lead to LSP violations as well, as developers, over time, start making assumptions around the default implementation, and/or start new-ing up instances using the default constructor.
 
-# Contact
-If you want to share your thoughts with the development team or join us you will be able to do so using the [official the mailing list](https://groups.google.com/forum/#!forum/inversifyjs).
+# Support
+If you are experience any kind of issues we will be happy to help. You can report an issue using the [issues page](https://github.com/inversify/InversifyJS/issues) or the [chat](https://gitter.im/inversify/InversifyJS). You can also ask questions at [Stack overflow](http://stackoverflow.com/tags/inversifyjs) using the `inversifyjs` tag.
 
-You can report issues using the [Github issues page](https://github.com/inversify/InversifyJS/issues).
+If you want to share your thoughts with the development team or join us you will be able to do so using the [official the mailing list](https://groups.google.com/forum/#!forum/inversifyjs). You can check out the [development wiki](https://github.com/inversify/InversifyJS/wiki) and browse the [documented source code](http://inversify.io/documentation/index.html) to learn more about InversifyJS internals.
 
 # License