[SCM] live-manual branch, debian-next, updated. debian/3.0_a14-1-26-g147eedc

[chals]

The following commit has been merged in the debian-next branch:
commit 147eedcb1162779d1914180bd60ac2c47baec5db
Author: chals <chals at altorricon.com>
Date:   Sun Aug 5 22:23:32 2012 +0200

    Proofreading project_bugs.

diff --git a/manual/en/project_bugs.ssi b/manual/en/project_bugs.ssi
index 8780c90..29f9d84 100644
--- a/manual/en/project_bugs.ssi
+++ b/manual/en/project_bugs.ssi
@@ -2,7 +2,7 @@ B~ Reporting bugs
 
 1~bugs Reporting bugs
 
-Debian Live is far from being perfect, but we want to make it as close as possible to perfect - with your help. Do not hesitate to report a bug: it is better to fill a report twice than never. However, this chapter includes recommendations how to file good bug reports.
+Debian Live is far from being perfect, but we want to make it as close as possible to perfect - with your help. Do not hesitate to report a bug. It is better to fill a report twice than never. However, this chapter includes recommendations on how to file good bug reports.
 
 For the impatient:
 
@@ -14,11 +14,11 @@ _* Try to give *{as specific information as possible}* about the bug. This inclu
 
 2~ Known issues
 
-Because Debian *{testing}* and Debian *{unstable}* distributions are a moving target, when you specify either as the target system distribution, a successful build may not always be possible.
+Since Debian *{testing}* and Debian *{unstable}* distributions are moving targets, when you specify either of them as the target system distribution, a successful build may not always be possible.
 
 % FIXME:
 
-If this causes too much difficulty for you, do not build a system based on *{testing}* or *{unstable}*, but rather, use *{stable}*. live-build does always default to the *{stable}* release.
+If this causes too much difficulty for you, do not build a system based on *{testing}* or *{unstable}*, but rather, use *{stable}*. live-build always defaults to the *{stable}* release.
 
 Currently known issues are listed under the section 'status' on our homepage at http://live.debian.net/.
 
@@ -34,7 +34,7 @@ Using outdated packages can cause significant problems when trying to reproduce
 
 2~collect-information Collect information
 
-Please provide enough information with your report. At least include the exact version of live-build version where the bug is encountered and steps to reproduce it. Please use common sense and include other relevant information if you think that it might help in solving the problem.
+Please provide enough information with your report. Include, at least, the exact version of live-build where the bug is encountered and the steps to reproduce it. Please use your common sense and provide any other relevant information if you think that it might help in solving the problem.
 
 To make the most out of your bug report, we require at least the following information:
 
@@ -56,7 +56,7 @@ _* Distribution of the live system
 
 _* Version of the kernel on the live system
 
-You can generate a log of the build process by using the #{tee}# command. We recommend doing this automatically with an #{auto/build}# script; (see {Managing a configuration}#managing-a-configuration for details).
+You can generate a log of the build process by using the #{tee}# command. We recommend doing this automatically with an #{auto/build}# script (see {Managing a configuration}#managing-a-configuration for details).
 
 code{
 
@@ -72,19 +72,19 @@ Remember to send in any logs that were produced with English locale settings, e.
 
 2~ Isolate the failing case if possible
 
-If possible, isolate the failing case to the smallest possible change that breaks. It is not always easy to do this, so if you can't manage it for your report, don't worry. However, if you plan your development cycle well, using small enough change sets per iteration, you may be able to isolate the problem by constructing a simpler 'base' configuration that closely matches your actual configuration plus just the broken change set added to it. If you have a hard time sorting out which of your changes broke, it may be that you are including too much in each change set and should develop in smaller increments.
+If possible, isolate the failing case to the smallest possible change that breaks. It is not always easy to do this so if you cannot manage it for your report, do not worry. However, if you plan your development cycle well, using small enough change sets per iteration, you may be able to isolate the problem by constructing a simpler 'base' configuration that closely matches your actual configuration plus just the broken change set added to it. If you have a hard time sorting out which of your changes broke, it may be that you are including too much in each change set and should develop in smaller increments.
 
 2~ Use the correct package to report the bug against
 
-If you don't know what component is responsible for the bug or if the bug is a general bug concerning live systems, you can fill a bug against the debian-live pseudo-package.
+If you do not know what component is responsible for the bug or if the bug is a general bug concerning live systems, you can fill a bug against the debian-live pseudo-package.
 
-However, we would appreciate if you try to narrow it down according to where the bug appears.
+However, we would appreciate it if you try to narrow it down according to where the bug appears.
 
 3~ At build time whilst bootstrapping
 
-live-build first bootstraps a basic Debian system with /{debootstrap}/ or /{cdebootstrap}/. Depending on the bootstrapping tool used and the Debian distribution it is bootstrapping, it may fail. If a bug appears here, check if the error is related to a specific Debian package (most likely), or if it is related to bootstrapping tool itself.
+live-build first bootstraps a basic Debian system with /{debootstrap}/ or /{cdebootstrap}/. Depending on the bootstrapping tool used and the Debian distribution it is bootstrapping, it may fail. If a bug appears here, check if the error is related to a specific Debian package (most likely), or if it is related to the bootstrapping tool itself.
 
-In both cases, this is not a bug in Debian Live, but rather in Debian itself which we can not fix this directly. Please report such a bug against the bootstrapping tool or the failing package.
+In both cases, this is not a bug in Debian Live, but rather in Debian itself and probably we cannot fix it directly. Please report such a bug against the bootstrapping tool or the failing package.
 
 3~ At build time whilst installing packages
 
@@ -92,23 +92,23 @@ live-build installs additional packages from the Debian archive and depending on
 
 If this is the case, this is not a bug in Debian Live, but rather in Debian - please report it against the failing package. Running /{debootstrap}/ separately from the Live system build or running #{lb bootstrap --debug}# will give you more information.
 
-Also, if you are using a local mirror and/or any of sort of proxy and you are experiencing a problem, please always reproduce it first by bootstrapping from an official mirror.
+Also, if you are using a local mirror and/or any sort of proxy and you are experiencing a problem, please always reproduce it first by bootstrapping from an official mirror.
 
 3~ At boot time
 
-If your image does not boot, please report it to the mailing list together with the information requested in {Collect information}#collect-information. Do not forget to mention, how/when the image failed, in Qemu, Virtualbox, VMWare or real hardware. If you are using a virtualization technology of any kind, please always run it on real hardware before reporting a bug. Providing a screenshot of the failure is also very helpful.
+If your image does not boot, please report it to the mailing list together with the information requested in {Collect information}#collect-information. Do not forget to mention, how/when the image failed, whether in Qemu, Virtualbox, VMWare or real hardware. If you are using a virtualization technology of any kind, please always run it on real hardware before reporting a bug. Providing a screenshot of the failure is also very helpful.
 
 3~ At run time
 
-If a package was successfully installed, but fails while actually running the Live system, this is probably a bug in Debian Live. However,
+If a package was successfully installed, but fails while actually running the Live system, this is probably a bug in Debian Live. However:
 
 2~ Do the research
 
-Before filing the bug, please search the web for the particular error message or symptom you are getting. As it is highly unlikely that you are the only person experiencing a particular problem, there is always a chance that it has been discussed elsewhere, and a possible solution, patch, or workaround has been proposed.
+Before filing the bug, please search the web for the particular error message or symptom you are getting. As it is highly unlikely that you are the only person experiencing a particular problem. There is always a chance that it has been discussed elsewhere and a possible solution, patch, or workaround has been proposed.
 
 You should pay particular attention to the Debian Live mailing list, as well as the homepage, as these are likely to contain the most up-to-date information. If such information exists, always include the references to it in your bug report.
 
-In addition, you should check the current bug lists for live-build, live-boot, live-config and live-tools to see whether something similar has been reported already.
+In addition, you should check the current bug lists for live-build, live-boot, live-config and live-tools to see whether something similar has already been reported.
 
 2~ Where to report bugs
 

-- 
live-manual