From a9331b62d77100cde6eec88a56b95d0b571754fe Mon Sep 17 00:00:00 2001
From: Maxim Sobolev <sobomax@FreeBSD.org>
Date: Mon, 4 Feb 2002 06:50:41 +0000
Subject: [PATCH] Minor readability changes.
---
en/gnome/docs/bugging.sgml | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/en/gnome/docs/bugging.sgml b/en/gnome/docs/bugging.sgml
index 3ac7f41875..c2f0e65abb 100644
--- a/en/gnome/docs/bugging.sgml
+++ b/en/gnome/docs/bugging.sgml
@@ -17,11 +17,11 @@
<p>The rule of the thumb should be: report as much information as you
can, because even if there is some irrelevant information usually
- developers could quite easy filter it out. On contrary, situation is
- much worse when there is too little information to reliably track down
- or reproduce the problem - in this case developers have to spend their
- time guessing and/or asking originator of report to send more
- information.</p>
+ developers could quite easy filter it out. On the contrary, the
+ situation is much worse when there is too little information to
+ reliably track down or reproduce the problem - in this case developers
+ have to spend their time guessing and/or asking originator of report
+ to send more information.</p>
<p>There are plenty of examples of totally useless bug reports, something
like <i>"Hey, gnomefoo port is broken. I'm running FreeBSD-X.Y.
@@ -56,7 +56,7 @@
<p>There are several ways to report a bug in GNOME running on a FreeBSD
system: you could send report to the
- <a href="mailto:freebsd-gnome@FreeBSD.org">freebsd-gnome mailing
+ <a href="mailto:&email;@FreeBSD.org">freebsd-gnome mailing
list</a>, file a problem report in
<a href="http://www.freebsd.org/support.html#gnats">FreeBSD bug
reporting system</a>, send your report to the particular GNOME