This is an automated email from the ASF dual-hosted git repository.

git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/openoffice-org.git


The following commit(s) were added to refs/heads/asf-staging by this push:
     new 6e4794c  git-site-role commit from build_staging.sh
6e4794c is described below

commit 6e4794cb8eff38a3b9a96691518840bb5731f960
Author: jenkins <bui...@apache.org>
AuthorDate: Mon Mar 22 14:30:23 2021 +0000

    git-site-role commit from build_staging.sh
---
 content/feed.xml                           | 4 ++--
 content/qa/issue_handling/basic_rules.html | 6 +++---
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/content/feed.xml b/content/feed.xml
index 828785e..577f0b0 100644
--- a/content/feed.xml
+++ b/content/feed.xml
@@ -6,8 +6,8 @@
     <atom:link href="http://localhost:8820/feed.xml"; rel="self" 
type="application/rss+xml" />
     <description>OpenOffice.org Feed</description>
     <language>en-us</language>
-    <pubDate>Mon, 22 Mar 2021 14:23:25 +0000</pubDate>
-    <lastBuildDate>Mon, 22 Mar 2021 14:23:25 +0000</lastBuildDate>
+    <pubDate>Mon, 22 Mar 2021 14:29:07 +0000</pubDate>
+    <lastBuildDate>Mon, 22 Mar 2021 14:29:07 +0000</lastBuildDate>
     
 
   </channel> 
diff --git a/content/qa/issue_handling/basic_rules.html 
b/content/qa/issue_handling/basic_rules.html
index e56e9d8..f6ed9ea 100644
--- a/content/qa/issue_handling/basic_rules.html
+++ b/content/qa/issue_handling/basic_rules.html
@@ -27,7 +27,7 @@
       
       
 <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>
@@ -111,7 +111,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/>
@@ -165,7 +165,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> =&gt; OpenOffice.org crashes</li>
+  <li> =&gt; 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

Reply via email to