3 files changed, 17 insertions, 4 deletions
diff --git a/scribus/doc/en/collect4output.html b/scribus/doc/en/collect4output.html
index d34cf85..f10ca6c 100644
--- a/scribus/doc/en/collect4output.html
+++ b/scribus/doc/en/collect4output.html
@@ -5,10 +5,10 @@
 </head>
 <body>
 <h2>Collect for Output</h2>
-<p>Collect for Output is a specialized way of saving a Scribus document.</p>
-<p>If you work with Scribus on a single computer in a noncollaborative way, you may never have a need for Collect for Output. If you work on more than one, and especially if they might have different operating systems, such as one with Linux and one with Windows, you may find this function useful. If you work collaboratively on a Scribus document, then this may be nearly essential, or at least very useful to know about.</p>
-<p>If you are highly organized, you may have a workflow in which you work with a Scribus project in its own directory, with all the images and other content in that directory. Even so, allowing someone else to work on the document may not be as simple as sending the project directory. You may find after the fact that some images were not there or that your collaborator doesn't have one of the fonts used in the document.</p>
-<p>You might want to use Collect for Output for your own needs, simply to bring all the elements of a document together in one directory as a convenience.</p>
+<p><i>Collect for Output</i> is a specialized way of saving a Scribus document.</p>
+<p>If you work with Scribus on a single computer in a noncollaborative way, you won't necessarily ever have a need for <i>Collect for Output</i>. If you work on more than one, and especially if they might have different operating systems, such as one with Linux and one with Windows, you may find this function useful. If you work collaboratively on a Scribus document, then this will be nearly essential, or at least very useful to know about.</p>
+<p>If you are highly organized, you probably have a workflow in which you work with a Scribus project in its own directory, with all the images and other content in that directory. Even so, allowing someone else to work on the document may not be as simple as sending the project directory, when you find after the fact that some images were not there or that your collaborator doesn't have one of the fonts used in the document.</p>
+<p><i>Collect for Output</i> could simply be useful for your own needs, to bring all the elements of a document together in one directory as a convenience.</p>
 <h3>The Process</h3>
 <p>In summary, what Collect for Output entails is creating a directory for your project, selecting that directory, then Scribus takes it from there, saving the document inside, along with its images, and if you wish, font files and color profiles. Technically, you do not need to create a new directory or choose an empty one, but for many uses, having only the files for the particular project in that directory would make the most sense.</p>
 <p>When the document is saved all of the links for the images are changed for the document copy in this new directory. Let's show an example.</p>
@@ -29,5 +29,18 @@
 <p>What has happened in Scribus is that you are now working with this new copy of the document, with its content here, instead of the original file and its content, however scattered it might have been. Open this file as you would any other document, by going to its directory and selecting the file.</p>
 <p>Conceptually you can see how this makes passing this back and forth between collaborators much more efficient. Also consider that you might choose to use Collect for Output to create several versions, with variations on the images for example, by repeating the Collect for Output procedure to some other directory.</p></td></tr>
 </table>
+<h3>Avoiding Trouble</h3>
+<table cellpadding="3" width="80%">
+<tr><td><p>Something you need to be careful about is moving or deleting any of these files outside of Scribus. To understand why this is, look at what happens.</p>
+<p>On the right is a depiction of our original situation, before running <i>Collect for Output</i>, where we have the Scribus document saved in one directory, and then perhaps images scattered around in others. When we run <i>Collect for Output</i>, all of these files are still in these locations.</p>
+<p>For each image, Scribus only has a relative path listed when you save the document &ndash; relative to where the <code>.sla</code> is saved.</p>
+<td><img src="images/collect_out5.png"></td></tr>
+<tr><td>&nbsp;</td></tr>
+<tr><td><p>Now that you have run <i>Collect for Output</i>, the document file is in your new directory, but so are copies of all the images, and all the relative links point to this new location. If you delete or move an image from the directory, the reference in the document is unchanged, so you have a missing image.</p>
+<p>One solution might be to go back to your original document and rerun <i>Collect for Output</i>, but this will lose any edits you have made in the file. Plan B in this situation might be to rename your collected file, go back to the original, Collect again, then revert the renamed file</p>
+<p>Otherwise, you face manually going through the original file to find the missing image, or some even more complicated scheme. Thus the warnings about moving/deleting files outside of Scribus.</p>
+<td><img src="images/collect_out6.png"></td></tr>
+
+</table>
 </body>
 </html>
diff --git a/scribus/doc/en/images/collect_out5.png b/scribus/doc/en/images/collect_out5.png
new file mode 100644
index 0000000..096fa76
--- /dev/null
+++ b/scribus/doc/en/images/collect_out5.png
diff --git a/scribus/doc/en/images/collect_out6.png b/scribus/doc/en/images/collect_out6.png
new file mode 100644
index 0000000..d00c205
--- /dev/null
+++ b/scribus/doc/en/images/collect_out6.png