Polishing

.github/CONTRIBUTING.md

@@ -2,36 +2,36 @@ _Elasticsearch is an open source project and we love to receive contributions fr
 
 Please read the [contributing guidelines][] which explain in detail how to contribute to Elasticsearch. The _short_ version is given below:
 
-# For questions, please use the forum not the issue tracker
+### For questions, please use the [forums](https://discuss.elastic.co/c/elasticsearch-and-hadoop) not the issue tracker
 
 If you need help and have questions, please use the [forums](https://discuss.elastic.co/c/elasticsearch-and-hadoop) to ask questions. If on the other hand the code does not behave appropriately and you bumped into an error, use the issue tracker.
 
-# Check the issue tracker
+## Check the issue tracker
 
 If you have a bug fix or new feature that you would like to contribute to Elasticsearch, please [find or open an issue][] about it first. Talk about what you would like to do. 
 It may be that somebody is already working on it, or that there are particular issues that you should know about before implementing the change.
 
 We enjoy working with contributors to get their code accepted. There are many approaches to fixing a problem and it is important to find the best approach before writing too much code.
 
-# Fork and clone the repository
+## Fork and clone the repository
 
 You will need to fork the main Elasticsearch code or documentation repository and clone it to your local machine. See [github documentation][] for help.
 
-## Submitting your changes
+### Submitting your changes
 
 Once your changes and tests are ready to submit for review:
-## Test your changes
+### Test your changes
 
 Run the test suite to make sure that nothing is broken.
-## Sign the Contributor License Agreement
+### Sign the Contributor License Agreement
 
 Please make sure you have signed our [Contributor License Agreement][]. We are not asking you to assign copyright to us, but to give us the right to distribute your code without restriction. We ask this of all contributors in order to assure our users of the origin and continuing existence of the code. You only need to sign the CLA once.
 
-## Rebase your changes
+### Rebase your changes
 
 Update your local repository with the most recent code from the main Elasticsearch repository, and rebase your branch on top of the latest master branch. We prefer your changes to be squashed into a single commit.
 
-## Submit a pull request
+### Submit a pull request
 
 Push your local changes to your forked copy of the repository and [submit a pull request][]. In the pull request, describe what your changes do and mention the number of the issue where discussion has taken place, eg “Closes #123″.
 

.github/ISSUE_TEMPLATE.md

@@ -1,3 +1,5 @@
+_For questions, please use the [forum](https://discuss.elastic.co/c/elasticsearch-and-hadoop) not the issue tracker_
+
 Make sure to fill the information below before submitting your issue -- thank you! 
 
 
@@ -14,7 +16,7 @@ Make sure to fill the information below before submitting your issue -- thank yo
 
 ### Issue description
 
-### Code snippets
+### Sample Configuration / Code
 
 Code:
 
@@ -31,6 +33,10 @@ Stack trace goes here
 ### Version Info
 
 Java        :
+
 Hadoop/Spark:
+
 ES-Hadoop   :
-ES          : 
+
+ES          :
+