openstack/openstack-manuals
Code Issues Proposed changes

Community Support Sentences

Browse Source 
Edit and adjust the sentences in Appendix A. Adjusted sentence length and clarity
for users seeking support, and restored comma aside to maintain voice.

Change-Id: Idf71e5caa757aba4b4771957b1a390ac3a586fd3
backport: none
Closes-Bug: #1304748
This commit is contained in:
Joseph Robinson 2014-04-09 13:00:46 +10:00
parent 14899c0c25
commit addcbdaa3a
1 changed files with 11 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
doc/common/app_support.xml
View File

@ -5,13 +5,12 @@
xml:id="app_community_support">
<?dbhtml stop-chunking?>
<title>Community support</title>
<para>Many resources are available to help you run and use
OpenStack. Members of the OpenStack community can answer
questions and help with bug suspicions. We are constantly
improving and adding to the main features of OpenStack, but if
you have any problems, do not hesitate to ask. Use the
following resources to get OpenStack support and troubleshoot
your existing installations.</para>
<para>The following resources are available to help you run and use
OpenStack. The OpenStack community constantly improves and
adds to the main features of OpenStack, but if you have
any questions, do not hesitate to ask. Use the
following resources to get OpenStack support,
and troubleshoot your installations.</para>
<section xml:id="support-documentation">
<title>Documentation</title>
<para>For the available OpenStack documentation, see <link
@ -208,7 +207,8 @@
to give a clear, concise summary in the title and provide
as much detail as possible in the description. Paste in
your command output or stack traces, links to screen
shots, and so on.</para>
shots, and any other information which
might be useful.</para>
</section>
<section xml:id="support-mailing-lists">
<title>OpenStack mailing lists</title>
@ -260,13 +260,14 @@
<listitem>
<para>Provide as much detail as possible in the
description. Paste in your command output or stack
traces, links to screen shots, and so on.</para>
traces, links to screen shots, and any
other information which might be useful.</para>
</listitem>
<listitem>
<para>Be sure to include the software and package
versions that you are using, especially if you are
using a development branch, such as,
<literal>"Grizzly release" vs git commit
<literal>"Icehouse release" vs git commit
bc79c3ecc55929bac585d04a03475b72e06a3208</literal>.</para>
</listitem>
<listitem>