Tweak the issue and the PR templates

Author: bbatsov

.github/ISSUE_TEMPLATE.md

@@ -1,16 +1,16 @@
-Use the template below when reporting bugs. Please, make sure that
-you're running the latest stable release or the latest snapshot of
-`cider-nrepl` and that the problem you're reporting hasn't been
-reported (and potentially fixed) already.
+*Use the template below when reporting bugs. Please, make sure that you're
+running the latest stable release or the latest snapshot/pre-release of
+`cider-nrepl` and that the problem you're reporting hasn't been reported (and
+potentially fixed) already.*
 
 ## Expected behavior
 
 ## Actual behavior
 
 ## Steps to reproduce the problem
 
-This is extremely important! Providing us with a reliable way to reproduce
-a problem will expedite its solution.
+*This is extremely important! Providing us with a reliable way to reproduce
+a problem will expedite its solution.*
 
 ## Environment & Version information
 

.github/PULL_REQUEST_TEMPLATE.md

@@ -6,11 +6,8 @@ Before submitting a PR make sure the following things have been done:
 - [ ] The new code is not generating reflection warnings
 - [ ] You've updated the README (if adding/changing middleware)
 
-Keep in mind that new cider-nrepl builds are automatically deployed to Clojars
-once a PR is merged, but **only** if the CI build is green.
-
-*If you're just starting out to hack on cider-nrepl you might find
-this [article](https://juxt.pro/blog/posts/nrepl.html) and the
+**Note:** If you're just starting out to hack on `cider-nrepl` you might find
+[nREPL's documentation](https://nrepl.org) and the
 "Design" section of the README extremely useful.*
 
 Thanks!