summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorlpsolit%gmail.com <>2008-04-04 13:48:02 +0200
committerlpsolit%gmail.com <>2008-04-04 13:48:02 +0200
commit2f8f717f011d1bfb36dfb4d7af7f521764343a3b (patch)
tree03bcbaa3ebf31bd10b2b0a032b0c70a31da37ab9
parentb543d4ecb8481484cb5f6d7341942a9f9ec695a9 (diff)
downloadbugzilla-2f8f717f011d1bfb36dfb4d7af7f521764343a3b.tar.gz
bugzilla-2f8f717f011d1bfb36dfb4d7af7f521764343a3b.tar.xz
Fixing bustage: &quote; -> <quote>
-rw-r--r--docs/en/xml/using.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/en/xml/using.xml b/docs/en/xml/using.xml
index ee9616e2f..abba39563 100644
--- a/docs/en/xml/using.xml
+++ b/docs/en/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>