summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authormkanat%bugzilla.org <>2006-05-05 23:10:57 +0200
committermkanat%bugzilla.org <>2006-05-05 23:10:57 +0200
commit0aeb1349243e6996a7a53e9faf01ac8d13e9e9b3 (patch)
tree5784f10bf250fcaa24127c5de91bab0499a21b08
parentb778d54f31e2b9d2cfee20c5b7b3331f36cb6835 (diff)
downloadbugzilla-0aeb1349243e6996a7a53e9faf01ac8d13e9e9b3.tar.gz
bugzilla-0aeb1349243e6996a7a53e9faf01ac8d13e9e9b3.tar.xz
Fix a typo in the Release Notes pointed out by RSZ.
-rw-r--r--docs/rel_notes.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/rel_notes.txt b/docs/rel_notes.txt
index 6dc1eecdd..909dba2fc 100644
--- a/docs/rel_notes.txt
+++ b/docs/rel_notes.txt
@@ -234,7 +234,7 @@ Optional "Strict Isolation" for Groups
--------------------------------------
If you turn on the "strict_isolation" parameter in Bugzilla, you
will *not* be able to add any user to the CC field (or set them
-as an Asignee or QA Contact) unless that user could normally see
+as an Assignee or QA Contact) unless that user could normally see
the bug. That is, you will no longer be able to "accidentally"
(or intentionally) give somebody access to a bug that they
otherwise couldn't see.