* Added more CSS control for menus, buttons, app names, shell commands, paths.

* Always wanting keyboard graphics for shortcuts, Jorge suggested simple borders
  for simplicity. Great idea! Added.
* Added Jorge's rounded boxes for note/warning/stop plus symbols.
* If anyone wants to fine tune esp. colours, go ahead. Jorge and I are both
  challenged in that department. :)
* A few small corrections and reformatting here and there.
* Excluded the topic "Installation" from the contents until it's further along.


git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@29269 a95241bf-73f2-0310-859d-f6bbb57e9c96

welcome/en/bugreports.html

@@ -41,12 +41,12 @@ Please follow these guidelines to create helpful bug reports:</p>
 <li><p>Mention which revision from <acronym title="Subversion, the source code management system we use">SVN</acronym> you are running. You can find this information in '<i>About This System...</i>' from the Deskbar menu.</p></li>
 <li><p>Describe the problem you are experiencing. Try to be as accurate as you can: describe the actual behavior, and the behavior you expected.</p></li>
 <li><p>Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.</p></li>
-<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the <tt>PRINT</tt> key files a <acronym title="Portable Network Graphics image format">PNG</acronym> into <tt>/boot/home/</tt>).</p>
-<p>If it is a hardware problem, include a copy of the <tt>syslog</tt> file (just query for "<tt>syslog</tt>" to find it).</p>
-<p>Also interesting when dealing with hardware issues, is the output of <tt>listdev</tt> and <tt>sysinfo</tt>. This will pipe the output into text files that you can attach to your bugreport or email:</p>
+<li><p>Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot (the <span class="key">PRINT</span> key files a <acronym title="Portable Network Graphics image format">PNG</acronym> into <span class="path">/boot/home/</span>).</p>
+<p>If it is a hardware problem, include a copy of the <span class="cli">syslog</span> file (just query for "<tt>syslog</tt>" to find it).</p>
+<p>Also interesting when dealing with hardware issues, is the output of <span class="cli">listdev</span> and <span class="cli">sysinfo</span>. This will pipe the output into text files that you can attach to your bugreport or email:</p>
 <pre class="terminal">listdev > listdev-output.txt
 sysinfo > sysinfo-output.txt</pre></li>
-<li><p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering "<tt>bt</tt>" into the launched debug Terminal, you create a "backtrace" that you should copy into your bugreport.</p></li>
+<li><p>When an application crashed, you should invoke the debugger from the alert that pops up. Entering <span class="cli">bt</span> into the launched debug Terminal, you create a "backtrace" that you should copy into your bugreport.</p></li>
 </ul></li>
 <li><p>After the bug has been reported, a developer will look at your bug and try to classify it. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding non-descriptive comments.</p></li>
 <li><p>Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Please stay around to answer these. Consider your participation 'done' when the bug is marked as 'fixed'. Together we can improve Haiku, bit by bit.</p></li>