Minor clarifications to the Mod docs conventions and whitespace clarifications

Author: vikram-redhat

contributing_to_docs/doc_guidelines.adoc

@@ -35,6 +35,11 @@ toc::[]                                                         <6>
 
 After the heading block and a single whitespace line, you can include any content for the topic.
 
+[NOTE]
+====
+Please set your editor to strip trailing whitespace.
+====
+
 [NOTE]
 ====
 The topic title, which is the first line of the document, is the only level 1 ( = ) title. Section headers within the topic must be level 2 ( == ) or lower.

contributing_to_docs/tools_and_setup.adoc

@@ -69,6 +69,7 @@ of the box, but if you are on Windows you can use http://cygwin.com/[Cygwin])
 * http://www.git-scm.com/[Git]
 * A web browser (Firefox, Chrome, or Safari) with the
 http://livereload.com/[LiveReload] extension installed
+* An editor that can strip trailing whitespace.
 
 === Install the required software dependencies on a Linux system
 The following instructions describe how to install all the required tools to do

modules/mod-docs-ocp-conventions.adoc

@@ -88,7 +88,11 @@ of the openshift-docs repository. These modules must follow the file naming
 conventions specified in the
 link:https://redhat-documentation.github.io/modular-docs/[modular docs guidelines].
 
-* All assemblies must go in the the relevant guide/book (MORE TO COME ON THIS).
+* All assemblies must go in the the relevant guide/book. If you can't find a relevant
+ guide/book, please reach out to a member of the OpenShift CCS team. So guides/books contain assemblies, which
+ contain modules.
+
+* modules and images folders are symlinked to the top level folder from each book/guide folder.
 
 * In your assemblies, when you are linking to the content in other books, you must
 use the relative path starting like so: