Update ISSUE_TEMPLATE.md

Author: zhenlineo

ISSUE_TEMPLATE.md

@@ -5,24 +5,25 @@ Firstly, if you are an Enterprise customer, you might want to head over to our [
 If you think you might have **hit a bug** in our software (it happens occasionally!) or you have specific **feature request** then use the issue feature on the relevant GitHub repository.
 Check first though as someone else may have already raised something similar.
 
-If you simply want to get started or have a question on how to use a particular feature, drop a line to the [mailing list](https://groups.google.com/forum/#!forum/neo4j), ask a question in [Slack](http://neo4j.com/slack), or [tweet](https://twitter.com/neo4j) us.
+If you simply want to get started or have a question on how to use a particular feature, ask a question in [Neo4j Online Community](https://community.neo4j.com/) instead.
 [StackOverflow](http://stackoverflow.com/questions/tagged/neo4j) also hosts a ton of questions and might already have a discussion around your problem.
 Make sure you have a look there too.
 
-If you want to make a feature request then there is no guideline, so feel free to stop reading and open an issue. 
+If you want to make a feature request, please prefix your issue title with `[Feature Request]` so that it is clear to us. 
 If you have a bug report however, please continue reading.  
 To help us understand your issue, please specify important details, primarily:
 
 - Neo4j version: Community/Enterprise X.Y.Z
 - Neo4j Mode: Single instance/HA cluster with X members/Casual cluster with X core Y read-replica
 - Driver version: X lanaguage driver X.Y.Z (If you use some other library that wraps around this driver, you might want to raise an issue there first)
-- Operating system: (for example Windows 95/Ubuntu 16.10 on AWS)
+- Operating system: (for example Windows 10/Ubuntu 16.10 on AWS)
 - **Steps to reproduce**
 - Expected behavior
 - Actual behavior
 
 Additionally, include (as appropriate) log-files, stacktraces, and other debug output.
-Always check the server logs too to see if there is any stacktrace related to the driver error.
+Always check the server logs to see if there is any stacktrace related to the driver error too.
+Aslo add any solutions you've tried to solve the problem yourself.
 
 ## Example bug report