This is an automated email from the ASF dual-hosted git repository.
digro pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git
The following commit(s) were added to refs/heads/main by this push:
new d1c7e7c Small changes
d1c7e7c is described below
commit d1c7e7c079b0d1e69375daa4f1652c289385bc10
Author: DiGro <[email protected]>
AuthorDate: Mon Mar 22 15:20:06 2021 +0100
Small changes
Changed Issue Tracker to Bugzilla
Changed OpenOffice.org to OpenOffice
---
content/qa/issue_handling/basic_rules.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/qa/issue_handling/basic_rules.html
b/content/qa/issue_handling/basic_rules.html
index 1963f64..0b4dda5 100644
--- a/content/qa/issue_handling/basic_rules.html
+++ b/content/qa/issue_handling/basic_rules.html
@@ -7,7 +7,7 @@
</head>
<body>
<div class="app">
-<h1>Basic IssueTracker rules</h1>
+<h1>Basic Bugzilla rules</h1>
<h3>Why you should read this</h3>
<p> Imagine how many people later on will read your issue (means the
issue which you submitted, or which you participated in) </p>
@@ -91,7 +91,7 @@ of an issue. "Spreadsheet problem" is less likely to be
handled
appropriately than "Spreadsheet: Data loss when ...." or "Label X in
dialog Y has a wrong offset (2 pixels)"</li>
</ul>
-Thus, please avoid summaries like "Big Bug in OpenOffice.org" or
+Thus, please avoid summaries like "Big Bug in OpenOffice" or
"Impress problem" - they are of no real help, and force people to waste
time to actually browse to the issue (instead of seeing it in a report)
to see what it is about.<br/>
@@ -145,7 +145,7 @@ You may be tempted to consider it stupid to write a
description like<br/>
all</span>"</li>
<li> from the context menu of the text, chose "<span
style="font-family: monospace;">Style|Bold</span>"</li>
- <li> => OpenOffice.org crashes</li>
+ <li> => OpenOffice crashes</li>
</ul>
Indeed there may be cases where this level of detail is
superfluous. But believe us, more often than not, it in the final
