[elpa] master b0aa5c2 48/51: Tweak bug-reporting information slightly

[Noam Postavsky]

branch: master
commit b0aa5c28162205f0aad20378d6a3f12a8b4ebe83
Author: João Távora <address@hidden>
Commit: João Távora <address@hidden>

    Tweak bug-reporting information slightly
    
    In the README and in the FAQ, mention and link to the list of support
    issues in the Github issue tracker.
    
    Rewrite README.mdown slightly for readability and suggest the GH
    tracker as primary place for YASnippet discussion.
    
    Retire the YASnippet google group.
    
    * README.mdown (Manual, issues, etc): Mention docs, support issues
    and issue tracker separately.  Remove reference to the YASnippet
    google group.
    (Where are the snippets?): Properly write YASnippet for
    consistency.
    
    * doc/faq.org: Add note and link to support issues.
---
 README.mdown | 24 ++++++++++++------------
 doc/faq.org  |  5 +++++
 2 files changed, 17 insertions(+), 12 deletions(-)

diff --git a/README.mdown b/README.mdown
index 2b25bdb..76772c8 100644
--- a/README.mdown
+++ b/README.mdown
@@ -55,7 +55,7 @@ where you want YASnippet enabled.
 
 <a name="import"></a>
 
-Yasnippet no longer bundles snippets directly, but it's very easy to
+YASnippet no longer bundles snippets directly, but it's very easy to
 get some!
 
 1. [yasnippet-snippets] - a snippet collection package maintained by
@@ -95,11 +95,16 @@ should be added like this to `yas-snippet-dirs`:
 
 # Manual, issues etc
 
-Please refer to the comprehensive [documentation][docs] for full
-customisation and support.  If you find a bug in the code or in the
-documentation, please report it to the main Emacs bug list,
address@hidden, and put "yasnippet" somewhere in the subject.
-Alternatively, you may use the [Github issue tracker][issues].
+There's comprehensive [documentation][docs] on using and customising
+YASnippet.
+
+There's a [list of support issues][support-issues], with solutions to
+common problems and practical snippet examples.
+
+The [Github issue tracker][issues] is where most YASnippet-related
+discussion happens.  Nevertheless, since YASnippet is a part of Emacs,
+you may alternatively report bugs to the main Emacs bug list,
address@hidden, putting "yasnippet" somewhere in the subject.
 
 ## Important note regarding bug reporting
 
@@ -147,16 +152,11 @@ do `git log -1` in the dir).
 Any more info is welcome, but don't just paste a backtrace or an error
 message string you got, unless we ask for it.
 
-There is also a [YASnippet google group][forum]. I will keep the group
-open for reference and for discussion among users. Unfortunately I
-can't guarantee a timely response, so maybe it's better to create a
-github issue clearly marking your intent (user support/bug/feature
-request).
-
 Finally, thank you very much for using YASnippet!
 
 [docs]: http://joaotavora.github.io/yasnippet/
 [issues]: https://github.com/joaotavora/yasnippet/issues
+[support-issues]: 
https://github.com/joaotavora/yasnippet/issues?q=label%3Asupport
 [googlecode tracker]: http://code.google.com/p/yasnippet/issues/list
 [forum]: http://groups.google.com/group/smart-snippet
 [melpa]: http://melpa.milkbox.net/
diff --git a/doc/faq.org b/doc/faq.org
index 64d4b99..9994e7b 100644
--- a/doc/faq.org
+++ b/doc/faq.org
@@ -2,6 +2,11 @@
 
 #+TITLE: Frequently Asked Questions
 
+-  *Note*: In addition to the questions and answers presented here,
+  you might also with to visit the list of 
[[https://github.com/joaotavora/yasnippet/issues?q=label%3Asupport][solved 
support issues]] in
+  the Github issue tracker.  It might be more up-to-date than this
+  list.
+
 * Why is there an extra newline?
 
 If there is a newline at the end of a snippet definition file,