summaryrefslogtreecommitdiffstats
path: root/docs/en/xml
diff options
context:
space:
mode:
authorvladd%bugzilla.org <>2008-04-04 13:48:12 +0200
committervladd%bugzilla.org <>2008-04-04 13:48:12 +0200
commit47738edc02c047bef91006128f87b33b5dab9ac2 (patch)
tree4e882ad119405234ed4615a03aa6a5132e0f16ad /docs/en/xml
parent01c0650ee3f6d093b2baf34beb866038bec4de5d (diff)
downloadbugzilla-47738edc02c047bef91006128f87b33b5dab9ac2.tar.gz
bugzilla-47738edc02c047bef91006128f87b33b5dab9ac2.tar.xz
Spell-patch ('Operarting' -> 'Operating') in the recently-added "Filing Bugs" documentation section, p=vladd.
Diffstat (limited to 'docs/en/xml')
-rw-r--r--docs/en/xml/using.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/en/xml/using.xml b/docs/en/xml/using.xml
index ca897e11c..40bde8e64 100644
--- a/docs/en/xml/using.xml
+++ b/docs/en/xml/using.xml
@@ -734,7 +734,7 @@
You now see a form where you can specify the component (part of
the product which is affected by the bug you discovered; if you have
no idea, just select <quote>General</quote> if such a component exists),
- the version of the program you were using, the Operarting System and
+ the version of the program you were using, the Operating System and
platform your program is running on and the severity of the bug (if the
bug you found crashes the program, it's probably a major or a critical
bug; if it's a typo somewhere, that's something pretty minor; if it's