summaryrefslogtreecommitdiffstats
path: root/docs/xml
diff options
context:
space:
mode:
authorlpsolit%gmail.com <>2006-11-24 05:58:40 +0100
committerlpsolit%gmail.com <>2006-11-24 05:58:40 +0100
commit01d7ece73f4d2db4e3d89b51e13a0463838f06bb (patch)
treea2fdf1e3a93a445d2e17219a20b4fbb5dc48997a /docs/xml
parent659ffdc2d049f7f38489ea0f779ae248df414eae (diff)
downloadbugzilla-01d7ece73f4d2db4e3d89b51e13a0463838f06bb.tar.gz
bugzilla-01d7ece73f4d2db4e3d89b51e13a0463838f06bb.tar.xz
Fixing bustage: &quote; -> <quote>
Diffstat (limited to 'docs/xml')
-rw-r--r--docs/xml/using.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/xml/using.xml b/docs/xml/using.xml
index ee9616e2f..abba39563 100644
--- a/docs/xml/using.xml
+++ b/docs/xml/using.xml
@@ -773,10 +773,10 @@
<para>
If you have a really large attachment, something that does not need to
be recorded forever (as most attachments are), you can mark your
- attachment as a &quote;Big File&quote;, assuming the administrator of the
+ attachment as a <quote>Big File</quote>, assuming the administrator of the
installation has enabled this feature. Big Files are stored directly on
disk instead of in the database, and can be deleted when it is no longer
- needed. The maximum size of a &quote;Big File&quote; is normally larger
+ needed. The maximum size of a <quote>Big File</quote> is normally larger
than the maximum size of a regular attachment.
</para>