diff options
author | timeless%mozdev.org <> | 2005-11-26 04:47:37 +0100 |
---|---|---|
committer | timeless%mozdev.org <> | 2005-11-26 04:47:37 +0100 |
commit | 320d2aa13e79d2d3ef938bf9f12b3c931a8bb3f7 (patch) | |
tree | 0dc5a31b9e6dc2a564b100a32c358b81ca844050 /contrib/bugmail_help.html | |
parent | 808e4b12c2e49be1bf1edafafd4c4c1ef2ddf226 (diff) | |
download | bugzilla-320d2aa13e79d2d3ef938bf9f12b3c931a8bb3f7.tar.gz bugzilla-320d2aa13e79d2d3ef938bf9f12b3c931a8bb3f7.tar.xz |
Bug 106386 Correct misspellings in source code
patch by unknown@simplemachines.org r=timeless rs=brendan
Diffstat (limited to 'contrib/bugmail_help.html')
-rw-r--r-- | contrib/bugmail_help.html | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/contrib/bugmail_help.html b/contrib/bugmail_help.html index a2f89f260..1b43cd2b5 100644 --- a/contrib/bugmail_help.html +++ b/contrib/bugmail_help.html @@ -39,7 +39,7 @@ You receive a reply mail with the new bug-ID if your request was ok. If not, you get a mail with some help on the bugmail system and a specific analysis of your request. <P> -Please dont refuse to send one or two wrong mails, you will get all the information +Please don't refuse to send one or two wrong mails, you will get all the information you need in the replies, and <I>only</I> in the mail replies. The information on this page, concerning available products, versions and so on, is not dynamicly generated and may be old therefore. @@ -91,23 +91,23 @@ hopefully valid value. <TR> <TD>@rep_platform</TD> <TD>The desired platform</TD> - <TD>no.<br>If you dont give a value, this field is set to <I>All</I>.</TD> + <TD>no.<br>If you don't give a value, this field is set to <I>All</I>.</TD> </TR> <TR> <TD>@bug_severity</TD> <TD>The severity of the bug</TD> - <TD>no. <br> If you dont give a value, this field is set to + <TD>no. <br> If you don't give a value, this field is set to <I>normal</I></TD> </TR> <TR> <TD>@priority</TD> <TD>The priority of the bug</TD> - <TD>no.<br>If you dont give a value, this field is set to <I>P3</I></TD> + <TD>no.<br>If you don't give a value, this field is set to <I>P3</I></TD> </TR> <TR> <TD>@op_sys</TD> <TD>The operating system</TD> - <TD>no.<br>If you dont give a value, this field is set to <I>Linux</I>.</TD> + <TD>no.<br>If you don't give a value, this field is set to <I>Linux</I>.</TD> </TR> <TR> <TD>@assigned_to</TD> @@ -150,7 +150,7 @@ Give string values for the most keys above. Some keywords require special value <ol> <li>E-Mail adresses: If you want to set the qa-contact, specify a email-adress for @qa_contact. The email must be known by bugzilla of course.</li> <li>Listvalues: Most of the values have to be one of a list of valid values. Try by sending -a mail and read the reply. Skip fields if you dont get help for them unless you dont know +a mail and read the reply. Skip fields if you don't get help for them unless you don't know which values you may choose.</li> <li>free Text: The descriptions may be free text. </li> <li>Special: The field groupset may be specified in different in three different kinds: @@ -181,7 +181,7 @@ Some of the values must be choosen from a list:<br> <p> After you have specified the required keywords and maybe some other value, you may -describe your bug. You dont need a keyword for starting your bug description. All +describe your bug. You don't need a keyword for starting your bug description. All text which follows the keyword block is handled as long description of the bug. <p> @@ -198,7 +198,7 @@ the attachment in bugzilla. <H1><A NAME="examplemail">Example Mail</A></H1> -See the example of the mail <b>body</b> (Dont forget to specify the short description +See the example of the mail <b>body</b> (Don't forget to specify the short description in the mail subject):<hr><pre> @product = Bugzilla |