Index: src/site/apt/guides/getting-started/index.apt
===================================================================
--- src/site/apt/guides/getting-started/index.apt	(revision 380706)
+++ src/site/apt/guides/getting-started/index.apt	(working copy)
@@ -132,6 +132,10 @@
  version and the shell script to execute. The working
  directory of the project will be prepended to the scripts path.
 
+ To specify the shell script to be executed, click on the shell project and
+ click "Add" under the "Build Definitions" section. This script should <<at least>>
+ be able to check out source from your repository and run Maven.
+
  <NOTE:> The SCM URL is a Maven SCM URL. Here's an example of what an
  SCM URL looks like:
  <<<scm:svn:http://svn.apache.org/repos/asf/maven/continuum/trunk>>>
Index: src/site/fml/about.fml
===================================================================
--- src/site/fml/about.fml	(revision 380706)
+++ src/site/fml/about.fml	(working copy)
@@ -93,17 +93,22 @@
         </p>
         <p>
           To checkout the continuum-site project from the ASF Subversion repository, download the Subversion client for
-          your platform and run: <code>svn co http://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-site</code>
+          your platform and run: <code>svn co https://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-site</code>
         </p>
         <p>
           To build the continuum-site project you will need to use Maven 2.  You can download Maven 2 from the <a 
           href="http://maven.apache.org/maven2/download.html">Downloads page on the Maven 2 project site</a>.  Once you
           have installed Maven 2 and added it to your <code>PATH</code>, you can build the Continuum project site by
-          executing the <code>site:site</code> goal with the following command: <code>m2 site:site</code>.
+          executing the <code>site:site</code> goal with the following command: <code>mvn site:site</code>.
           After executing the <code>site:site</code> goal, the Continuum site will be stored in the
           <code>target/site</code> directory.
         </p>
         <p>
+          If you receive an error resolving the artifact <code>continuum-parent</code>, download the parent pom.xml from <a 
+          href="http://svn.apache.org/repos/asf/maven/continuum/trunk/pom.xml">here</a> and place it in the directory above your
+          <code>continuum-site</code> directory.  Then try the build again.
+        </p>
+        <p>
           Once you have updated the documentation, generate a patch by running <code>svn diff > site-patch.txt</code>.  Create a
           new issue in the Continuum JIRA project, and attach your patch to this issue.  Before submitting the patch, make sure
           to build the Continuum site locally and proofread for any typos.
Index: src/site/fml/faqs.fml
===================================================================
--- src/site/fml/faqs.fml	(revision 380706)
+++ src/site/fml/faqs.fml	(working copy)
@@ -125,6 +125,28 @@
         </p>
       </answer>
     </faq>
-
+    <faq id="build-entire-project-recursively-from-parent">
+      <question>How can I build the entire project recursively from the parent?</question>
+      <answer>
+        <p>
+          If you want to build recursively from the parent, you have to remove the <code>--non-recursive</code> or <code>-N</code> argument under the
+          "Build Definitions" section of your parent project.
+        </p>
+        <p>
+          Ensure that your entire project can be checked out using the SCM URL in your parent project.
+        </p>
+        <p>
+          For CVS users who have each child project in a separate module, you have several options:
+          <p>
+          <ui>
+            <li>Refactor the CVS directory structure to a more standard one (i.e. a module with the parent POM at the base and child projects as subdirectories)</li>
+            <li>Keep the structure and create a new module that contains a parent POM and a list of symbolic links to your actual CVS modules</li>
+          </ui>
+          </p>
+          These options ensure that your child projects will not be checked out into separate numbered working directories. Instead, they will be checked out
+          correctly under a single working directory.
+        </p>
+      </answer>
+    </faq>
   </part>
 </faqs>