r17633 by gpittman - minor color docs edit

[scribus-commit]

Author: gpittman
Date: Mon Jun 25 12:38:40 2012
New Revision: 17633

URL: http://scribus.net/websvn/listing.php?repname=Scribus&sc=1&rev=17633
Log:
minor color docs edit

Modified:
    trunk/Scribus/doc/en/color2.html

Modified: trunk/Scribus/doc/en/color2.html
URL: http://scribus.net/websvn/diff.php?repname=Scribus&rev=17633&path=/trunk/Scribus/doc/en/color2.html
==============================================================================
--- trunk/Scribus/doc/en/color2.html (original)
+++ trunk/Scribus/doc/en/color2.html Mon Jun 25 12:38:40 2012
@@ -15,8 +15,8 @@
 <li><strong>With a document open:</strong> In this case, selecting another color set will <strong><i>add</i></strong> the new palette’s colors to those you had previously. This new palette will be saved with the document. If you think you may wish to use it again, you would be wise to give it its own name so you can find it later.</li>
 </ul>
 <blockquote>
-<h3><font color="red">Caution!</font></h3>
-<p>Previous versions of the documentation have indicated that colors in the color sets included with Scribus are locked – this may not be the case, since it is dependent on where the palettes are stored on your system, and whether you have write access there. If you are editing colors with no document open, with a customized location for Scribus, you may be able to edit any color from any palette. If you then click <strong>Save</strong>, you have changed this palette for future use. On the other hand, if you have a document open, make such a change and <strong>Save</strong>, you will only change this color for that particular document. Even so, it is probably not a good idea to do this, so that you avoid confusion, since if you import something from that document to another, there may be unexpected problems due to the color name clash.</p>
+<h4><font color="red">Caution!</font></h4>
+<p>Previous versions of the documentation have indicated that colors in the color sets included with Scribus are locked – this may not be the case, since it is dependent on where the palettes are stored on your system, and whether you have write access there. If you are editing colors with no document open, with a customized location for Scribus, you may be able to edit any color from any palette. If you then click <strong>OK</strong>, you have changed this palette for future use. On the other hand, if you have a document open, make such a change and <strong>OK</strong>, you will only change this color for that particular document. Even so, it is probably not a good idea to do this, so that you avoid confusion, since if you import something from that document to another, there may be unexpected problems due to the color name clash.</p>
 <p>For proprietary spot colors, the color name will dictate what will be applied, so changing its appearance in Scribus will be another source of confusion and error.</p>
 </blockquote>
 <p>What you may notice when you open the dialog is that you can’t edit any color in one of the palettes that are shipped with Scribus (but see the above caution). This is a feature, not a bug, as the very purpose of standardized colors is to work across documents, computers or platforms with identical colors, which in turn have unique color values and color names. Thus, all color palettes that have been installed to directories to which you have read-only access are “locked”, i.e. prevented from editing.</p>