From 165b71a65c2c5df2cea8412fa1c9c3d0eed4eac7 Mon Sep 17 00:00:00 2001
From: Adam Weinberger Your environment (output of /usr/bin/env).
If you are building from ports, note approximately how
long it has been since you last updated your ports tree. If
- it has been more than a day, or if you haven't run
- portupgrade -a, don't bother sending a bug report
- until you've run cvsup and portupgrade.
Information specific for each type of breakage:
If you have a solution or a workaround for the problem, then include it into your report as well, even if you are not quite sure that - it is a proper fix. Even if the fix isn't quite right, it could still + it is a proper fix. Even if the fix is not quite right, it could still point others in the right direction.
@@ -86,7 +86,7 @@ FreeBSD bug reporting system.If the problem has to do with an application's - behaviour, report the problem directly to the applicaiton's + behaviour, report the problem directly to the application's developers through the GNOME project's bug tracking system
If the problem is quite serious, not necessarily diff --git a/en/gnome/docs/develfaq.sgml b/en/gnome/docs/develfaq.sgml index 8be9ecc162..c783430a22 100644 --- a/en/gnome/docs/develfaq.sgml +++ b/en/gnome/docs/develfaq.sgml @@ -1,6 +1,6 @@ - + %gnomeincludes; %includes; @@ -151,7 +151,7 @@ STRIP= this applet to marcus@FreeBSD.org.
-Even if you don't like working directly with code, we need +
Even if you do not like working directly with code, we need reports on experiences upgrading from GNOME &gnomever; to GNOME &gnomedevelver;; we need information on which apps are exhibiting strange behavior; we need to know in advance everything that an diff --git a/en/gnome/docs/faq2.sgml b/en/gnome/docs/faq2.sgml index b84a58da04..124304e289 100644 --- a/en/gnome/docs/faq2.sgml +++ b/en/gnome/docs/faq2.sgml @@ -1,6 +1,6 @@ - + %gnomeincludes; %includes; @@ -135,7 +135,7 @@ exec gnome-session
Updating solves most problems
-If you haven't yet followed FAQ #6, do so, as +
If you have not yet followed FAQ #6, do so, as it will most likely fix the problem you are reading this document to solve.
@@ -226,7 +226,7 @@ options _KPOSIX_PRIORITY_SCHEDULINGAfter running the above commands, you will have to reinstall all the GNOME applications you desire. This process sounds painful, but it is actually a great way to clear cruft off of your system. - Just install applications as you need them, and you'll be surprised + Just install applications as you need them, and you will be surprised how much disk space you have reclaimed. A full rebuild does take a significant amount of time; fortunately, this measure is only rarely needed.
diff --git a/en/gnome/docs/faq26.sgml b/en/gnome/docs/faq26.sgml index 2af4580f59..6d3400218e 100644 --- a/en/gnome/docs/faq26.sgml +++ b/en/gnome/docs/faq26.sgml @@ -1,6 +1,6 @@ - + %gnomeincludes; %includes; @@ -102,7 +102,7 @@$ tail -f /path/to/logfile-
you can watch the entire upgrade process as it unfolds. It's hypnotic!
+you can watch the entire upgrade process as it unfolds. It is hypnotic!
The upgrade failed; what do I do?
-Unfortunately, this is not only possible, it's highly probable. There are many possible +
Unfortunately, this is not only possible, it is highly probable. There are many possible valid GNOME configurations, and even more invalid starting points. If the script fails, follow the instructions in the error message to let the FreeBSD GNOME team know about the failure.
@@ -144,7 +144,7 @@ $ tail -f /path/to/logfile