fix: review from @bstaletic

Author: henryiii

.github/CONTRIBUTING.md

@@ -69,8 +69,8 @@ Tips:
 
 * You can use `virtualenv` (from PyPI) instead of `venv` (which is Python 3
   only).
-* You can select any name for your environment folder.
-* If you use a different shell, there are other activate scripts.
+* You can select any name for your environment folder; if it contains "env" it
+  will be ignored by git.
 * If you don’t have CMake 3.14+, just add “cmake” to the pip install command.
 * You can use `-DPYBIND11_FINDPYTHON=ON` instead of setting the
   `PYTHON_EXECUTABLE` - the new search algorithm can find virtual environments,
@@ -105,13 +105,12 @@ The valid options are:
 * Use `cmake build -LH` to list the CMake options with help.
 * Use `ccmake` if available to see a curses (terminal) gui, or `cmake-gui` for
   a completely graphical interface (not present in the PyPI package).
-* Use `-G` and the name of a generator to use something other than `make`, like
-  `Xcode` or `Ninja` (automatic multithread!).
+* Use `-G` and the name of a generator to use something different, like `Ninja`
+  (automatic multithreading!). `cmake --help` lists the generators available.
 * Open the `CMakeLists.txt` with QtCreator to generate for that IDE.
 * Use `cmake --build build -j12` to build with 12 cores (for example).
-* If you are using the `llvm` tool-suite, you can use
-  `-DCMAKE_EXPORT_COMPILE_COMMANDS=ON` to generate the .json file that the
-  `clang-*` commands expect.
+* You can use `-DCMAKE_EXPORT_COMPILE_COMMANDS=ON` to generate the `.json` file
+  that some tools expect.
 
 </p></details>
 

.github/ISSUE_TEMPLATE/bug-report.md

@@ -7,9 +7,14 @@ title: "[BUG] "
 
 Make sure you've completed the following steps before submitting your issue -- thank you!
 
-1. Make sure you've read the [documentation](http://pybind11.readthedocs.io/en/latest/). Your issue may be addressed there.
-2. Consider asking first in the [Gitter chat room](https://gitter.im/pybind/Lobby).
-3. Include a self-contained and minimal piece of code that reproduces the problem. If that's not possible, try to make the description as clear as possible.
+1. Make sure you've read the [documentation][]. Your issue may be addressed there.
+2. Search the [issue tracker][] to verify that this hasn't already been reported. +1 or comment there if it has.
+3. Consider asking first in the [Gitter chat room][].
+4. Include a self-contained and minimal piece of code that reproduces the problem. If that's not possible, try to make the description as clear as possible.
+
+[documentation]: https://pybind11.readthedocs.io
+[issue tracker]: https://github.com/pybind/pybind11/issues
+[Gitter chat room]: https://gitter.im/pybind/Lobby
 
 *After reading, remove this checklist and the template text in parentheses below.*
 

.github/ISSUE_TEMPLATE/feature-request.md

@@ -8,7 +8,9 @@ title: "[FEAT] "
 Make sure you've completed the following steps before submitting your issue -- thank you!
 
 1. Check if your feature has already been mentioned / rejected / planned in other issues.
-2. If those resources didn't help, consider asking in the [Gitter chat room](https://gitter.im/pybind/Lobby) to see if this is interesting / useful to a larger audience and possible to implement reasonably,
+2. If those resources didn't help, consider asking in the [Gitter chat room][] to see if this is interesting / useful to a larger audience and possible to implement reasonably,
 4. If you have a useful feature that passes the previous items (or not suitable for chat), please fill in the details below.
 
+[Gitter chat room]: https://gitter.im/pybind/Lobby
+
 *After reading, remove this checklist.*

.github/ISSUE_TEMPLATE/question.md

@@ -6,10 +6,16 @@ title: "[QUESTION] "
 
 If you have a question, please check the following first:
 
-1. Check if your question has already been answered in the [FAQ](http://pybind11.readthedocs.io/en/latest/faq.html) section.
-2. Make sure you've read the [documentation](http://pybind11.readthedocs.io/en/latest/). Your issue may be addressed there.
-3. If those resources didn't help and you only have a short question (not a bug report), consider asking in the [Gitter chat room](https://gitter.im/pybind/Lobby).
-4. If you have a more complex question which is not answered in the previous items (or not suitable for chat), please fill in the details below.
-5. Include a self-contained and minimal piece of code that illustrates your question. If that's not possible, try to make the description as clear as possible.
+1. Check if your question has already been answered in the [FAQ][] section.
+2. Make sure you've read the [documentation][]. Your issue may be addressed there.
+3. If those resources didn't help and you only have a short question (not a bug report), consider asking in the [Gitter chat room][]
+4. Search the [issue tracker][], including the closed issues, to see if your question has already been asked/answered. +1 or comment if it has been asked but has no answer.
+5. If you have a more complex question which is not answered in the previous items (or not suitable for chat), please fill in the details below.
+6. Include a self-contained and minimal piece of code that illustrates your question. If that's not possible, try to make the description as clear as possible.
+
+[FAQ]: http://pybind11.readthedocs.io/en/latest/faq.html
+[documentation]: https://pybind11.readthedocs.io
+[issue tracker]: https://github.com/pybind/pybind11/issues
+[Gitter chat room]: https://gitter.im/pybind/Lobby
 
 *After reading, remove this checklist.*