summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorvladd%bugzilla.org <>2007-03-10 08:48:47 +0100
committervladd%bugzilla.org <>2007-03-10 08:48:47 +0100
commit1d02c4bdd74ddb25b1265ffc131d8a0476cb78d1 (patch)
tree149e7bd21b7db9ba869a21f3023e3c552defe8bf /docs
parentfd4f00bd1bb1ce5ac70298b43087d253080aeeca (diff)
downloadbugzilla-1d02c4bdd74ddb25b1265ffc131d8a0476cb78d1.tar.gz
bugzilla-1d02c4bdd74ddb25b1265ffc131d8a0476cb78d1.tar.xz
Spell-patch ('Operarting' -> 'Operating') in the recently-added "Filing Bugs" documentation section, p=vladd.
Diffstat (limited to 'docs')
-rw-r--r--docs/xml/using.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/xml/using.xml b/docs/xml/using.xml
index ca897e11c..40bde8e64 100644
--- a/docs/xml/using.xml
+++ b/docs/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