r18793 by gpittman - Some minor edits to bug report doc

[scribus-commit]

Author: gpittman
Date: Sun Feb  2 15:59:22 2014
New Revision: 18793

URL: http://scribus.net/websvn/listing.php?repname=Scribus&sc=1&rev=18793
Log:
Some minor edits to bug report doc

Modified:
    trunk/Scribus/doc/en/bugreport.html

Modified: trunk/Scribus/doc/en/bugreport.html
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=18793&path=/trunk/Scribus/doc/en/bugreport.html
==============================================================================
--- trunk/Scribus/doc/en/bugreport.html (original)
+++ trunk/Scribus/doc/en/bugreport.html Sun Feb  2 15:59:22 2014
@@ -14,17 +14,14 @@
 
 <h2>Creating an Account</h2>
 
-<p>First, visit the <a href="http://bugs.scribus.net/signup_page.php">sign-up page</a>. You will see a page that looks like this:</p>
-<br>
-<table width="100%"><tr><td align="center"><img src="images/Mantis_signup.png"/></td></tr></table>
-<br>
-<p>Enter a login name, your e-mail address and the digits displayed. Then click “Signup” and wait until your account has been confirmed and you received a password via e-mail. You can change your personal preferences any time in the tab “My account,” provided you are logged in. Please take the time to check the different options. They may or may not be useful to you.</p>
+<p>While there is a <a href="http://bugs.scribus.net/signup_page.php">sign-up page</a>, account creation by anyone but administrators had to be disabled due to massive spam attacks. If you want to contribute by reporting bugs or requests for enhancements, you can either write an email to the <a href="mailing_lists.html">developer mailing list</a> or contact a member of the Scribus Team directly, who will then create an account for you.</p>
+<p>Once your account has been confirmed and you received a password via e-mail, you can change your personal preferences any time in the tab “My account,” provided you are logged in. Please take the time to check the different options. They may or may not be useful to you.</p>
 
 <h2>Before Filing a Bug Report</h2>
 <p>If something doesn’t work as expected, or you think you have the idea of the century, please don’t start firing up bug reports galore. Chances are that someone has already had the same problem, perhaps even the same great idea. Five steps are recommended to ensure your report won’t be closed as “Duplicate” or “No change required”.</p>
 
 <ol>
-<li>Read the <a href="http://docs.scribus.net/">Scribus Online Documentation</a>, rummage the <a href="http://wiki.scribus.net/index.php">Scribus Wiki</a>, or even consider buying the Official Scribus Manual. There are lots of informations in different languages available, and perhaps someone has already turned his own experiences into a Wiki article, or the documentation team may have documented a feature/issue thoroughly by then.</li>
+<li>Read the <a href="http://docs.scribus.net/">Scribus Online Documentation</a>, rummage the <a href="http://wiki.scribus.net/index.php">Scribus Wiki</a>, or even consider buying the Official Scribus Manual. There is a lot of information available in various languages, and perhaps someone has already turned his own experiences into a Wiki article, or the documentation team may have documented a feature/issue thoroughly by then.</li>
 <li>Try to really use Scribus and learn about its concepts. The use of Scribus is not hard to learn, but it is still <a href="about2.html">quite different</a> from, say, a word processor.</li>
 <li>Post your problem or your idea on one of the <a href="mailing_lists.html">mailing lists</a>. Things normally get sorted out quickly. Often enough, a supposed bug is just lack of experience.</li>
 <li>Ask questions on <a href="irc.html">IRC</a>. This is especially useful for “real time” support.</li>
@@ -67,7 +64,7 @@
 <br>
 
 <ul><li><i>Summary</i>: A short description of your report. This will become the “headline” in the bug tracker.</li>
-<li><i>Description</i>: Describe your issue as precisely as possible, but keep it concise. <b>Please don’t write any novels here!</b> It may also be helpful to upload some screenshots (see below). If you file a feature request, please add a real world scenario. The team needs examples to understand what the idea is and how this new feature would help people to work better and more efficiently. In other words, try to describe not only <i>what</i> and <i>how</i>, but also <i>why</i>.</li>
+<li><i>Description</i>: Describe your issue as precisely as possible, but keep it concise – <em>please don’t write any novels here!</em> It may also be helpful to upload some screenshots (see below). If you file a feature request, please add a real world scenario. The team needs examples to understand what the idea is and how this new feature would help people to work better and more efficiently. In other words, try to describe not only <i>what</i> and <i>how</i>, but also <i>why</i>.</li>
 <li><i>Steps to reproduce</i>: If you are able to reproduce a bug, please write down the steps necessary for reproduction on other computers.</li>
 <li><i>Additional information</i>: If you think other information, e.g. postings from the mailing list or messages from a debugger</a>, are useful in this context, you can add them here.</li>
 </ul>