summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjocuri%softhome.net <>2008-04-04 13:48:19 +0200
committerjocuri%softhome.net <>2008-04-04 13:48:19 +0200
commitb48967ede1ee3d83de9980b28e4978b72e35de02 (patch)
tree5fbad7caab099e421b38611fc9f414de232e2eb7
parent09e8640ba739b46d61278e27f7318801a7b68d44 (diff)
downloadbugzilla-b48967ede1ee3d83de9980b28e4978b72e35de02.tar.gz
bugzilla-b48967ede1ee3d83de9980b28e4978b72e35de02.tar.xz
Documentation patch: fix 'vunerabilites'->'vulnerabilities' spelling.
-rw-r--r--docs/en/xml/security.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/en/xml/security.xml b/docs/en/xml/security.xml
index 96ec5c897..351283b2c 100644
--- a/docs/en/xml/security.xml
+++ b/docs/en/xml/security.xml
@@ -1,5 +1,5 @@
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> -->
-<!-- $Id: security.xml,v 1.11 2008/04/04 06:48:18 jocuri%softhome.net Exp $ -->
+<!-- $Id: security.xml,v 1.12 2008/04/04 06:48:19 jocuri%softhome.net Exp $ -->
<chapter id="security">
<title>Bugzilla Security</title>
@@ -141,7 +141,7 @@
have no other reason to access MySQL remotely, then you should disable
the network access. This, along with the suggestion in
<xref linkend="security-os-ports"/>, will help protect your system from
- any remote vulnerabilites in MySQL.
+ any remote vulnerabilities in MySQL.
</para>
<example id="security-mysql-network-ex">