PHPTR Edit 2. More to come.

(This used to be commit bc4d2f60cefa126415b06440280761d19e8c0d21)

1 files changed, 22 insertions, 22 deletions

diff --git a/docs/Samba3-HOWTO/TOSHARG-Bugs.xml b/docs/Samba3-HOWTO/TOSHARG-Bugs.xml
index 5af66fc05a..1395d8893b 100644
--- a/docs/Samba3-HOWTO/TOSHARG-Bugs.xml
+++ b/docs/Samba3-HOWTO/TOSHARG-Bugs.xml
@@ -24,15 +24,15 @@ may be changing the bug reporting mechanism at some point.
 <para>
 Please do as much as you can yourself to help track down the
 bug. Samba is maintained by a dedicated group of people who volunteer
-their time, skills and efforts. We receive far more mail than
+their time, skills, and efforts. We receive far more mail than
 we can possibly answer, so you have a much higher chance of a response
-and a fix if you send us a <quote>developer friendly</quote> bug report that lets
+and a fix if you send us a <quote>developer-friendly</quote> bug report that lets
 us fix it fast. 
 </para>
 
 <para>
-Do not assume that if you post the bug to the comp.protocols.smb
-newsgroup or the mailing list that we will read it. If you suspect that your 
+If you post the bug to the comp.protocols.smb
+newsgroup or the mailing list, do not assume that we will read it. If you suspect that your 
 problem is not a bug but a configuration problem, it is better to send 
 it to the Samba mailing list, as there are thousands of other users on
 that list who may be able to help you.
@@ -52,7 +52,7 @@ at <ulink noescape="1" url="http://samba.org/samba/">http://samba.org/samba/</ul
 <para>
 Before submitting a bug report, check your config for silly
 errors. Look in your log files for obvious messages that tell
-you've mis-configured something. Run testparm to check your config
+you've misconfigured something. Run testparm to check your config
 file for correct syntax.
 </para>
 
@@ -76,7 +76,7 @@ If the bug has anything to do with Samba behaving incorrectly as a
 server (like refusing to open a file), then the log files will probably
 be quite useful. Depending on the problem, a log level of between 3 and
 10 showing the problem may be appropriate. A higher level gives more
-detail, but may use too much disk space.
+detail but may use too much disk space.
 </para>
 
 <para>
@@ -95,9 +95,9 @@ To do this, add the following lines to your main &smb.conf; file:
 <para>
 and create a file <filename>/usr/local/samba/lib/smb.conf.<replaceable>machine</replaceable></filename> where
 <replaceable>machine</replaceable> is the name of the client you wish to debug. In that file
-put any &smb.conf; commands you want, for example 
+put any &smb.conf; commands you want; for example, 
 <smbconfoption name="log level"/> may be useful. This also allows you to 
-experiment with different security systems, protocol levels and so on, on just 
+experiment with different security systems, protocol levels, and so on, on just 
 one machine.
 </para>
 
@@ -118,12 +118,12 @@ prepared for a large volume of log data.
 </para>
 
 	<sect2>
-	<title>Debugging Specific Operations</title>
+	<title>Debugging-Specific Operations</title>
 
 	<para>
 	Samba-3.x permits debugging (logging) of specific functional components without unnecessarily
 	cluttering the log files with detailed logs for all operations. An example configuration to 
-	achive this is shown in:
+	achieve this is shown in:
 	</para>
 
 <para>
@@ -136,10 +136,10 @@ prepared for a large volume of log data.
 
 	<para>
 	This will cause the level of detail to be expanded to the debug class (log level) passed to
-	each funtional area per the value shown above. The first value passed to the <parameter>log level</parameter>
+	each functional area per the value shown above. The first value passed to the <parameter>log level</parameter>
 	of <constant>0</constant> means turn off all unnecessary debugging except the debug classes set for
-	the functional areas as specified. The table shown in <link linkend="dbgclass">Debugable Functions</link>
-	may be used to affect very precise analysis of each SMB operation Samba is conducting.
+	the functional areas as specified. The table shown in <link linkend="dbgclass">Debuggable Functions</link>
+	may be used to attain very precise analysis of each SMB operation Samba is conducting.
 	</para>
 
 	<table frame="all" id="dbgclass">
@@ -178,7 +178,7 @@ you have faulty hardware or system software).
 <para>
 If the message came from smbd, it will probably be accompanied by
 a message that details the last SMB message received by smbd. This
-information is often useful in tracking down the problem so please
+information is often useful in tracking down the problem, so please
 include it in your bug report.
 </para>
 
@@ -212,7 +212,7 @@ problem occurred. Include this in your report.
 
 <para>
 If you know any assembly language, do a <command>disass</command> of the routine
-where the problem occurred (if its in a library routine, then
+where the problem occurred (if it's in a library routine, then
 disassemble the routine that called it) and try to work out exactly
 where the problem is by looking at the surrounding code. Even if you
 do not know assembly, including this information in the bug report can be
@@ -225,10 +225,10 @@ useful.
 
 <para>
 Unfortunately, some UNIXes (in particular some recent Linux kernels)
-refuse to dump a core file if the task has changed uid (which smbd
+refuse to dump a core file if the task has changed UID (which smbd
 does often). To debug with this sort of system, you could try to attach
 to the running process using
-<userinput>gdb smbd <replaceable>PID</replaceable></userinput> where you get
+<userinput>gdb smbd <replaceable>PID</replaceable></userinput>, where you get
 <replaceable>PID</replaceable> from <application>smbstatus</application>.
 Then use <command>c</command> to continue and try to cause the core dump
 using the client. The debugger should catch the fault and tell you
@@ -236,7 +236,7 @@ where it occurred.
 </para>
 
 <para>
-Sometimes it is necessary to build a Samba binary files that have debugging
+Sometimes it is necessary to build Samba binary files that have debugging
 symbols so as to make it possible to capture enough information from a crashed
 operation to permit the Samba Team to fix the problem.
 </para>
@@ -247,13 +247,13 @@ Add the following line to the &smb.conf; file global section:
 <screen>
 panic action = "/bin/sleep 90000"
 </screen>
-to catch any panics. If <command>smbd</command> seems to be frozen look for any sleep
-processes. If it is not, and appears to be spinning, find the process id
+to catch any panics. If <command>smbd</command> seems to be frozen, look for any sleep
+processes. If it is not, and appears to be spinning, find the PID
 of the spinning process and type:
 <screen>
 gdb /usr/local/samba/sbin/smbd
 </screen>
-then <quote>attach 'pid'</quote> (of the spinning process), then type <quote>bt</quote> to
+then <quote>attach `pid'</quote> (of the spinning process), then type <quote>bt</quote> to
 get a backtrace to see where the smbd is in the call path.
 </para>
 
@@ -268,7 +268,7 @@ get a backtrace to see where the smbd is in the call path.
 <indexterm><primary>patch</primary></indexterm>
 The best sort of bug report is one that includes a fix! If you send us
 patches, please use <userinput>diff -u</userinput> format if your version of 
-diff supports it, otherwise use <userinput>diff -c4</userinput>. Make sure 
+diff supports it; otherwise, use <userinput>diff -c4</userinput>. Make sure 
 you do the diff against a clean version of the source and let me know 
 exactly what version you used. 
 </para>