diff -r c7c26511138f -r 7c4a911dc066 buildframework/helium/doc/src/manual/stage_preparation.rst.inc.ftl
--- a/buildframework/helium/doc/src/manual/stage_preparation.rst.inc.ftl	Wed Jun 16 16:51:40 2010 +0300
+++ b/buildframework/helium/doc/src/manual/stage_preparation.rst.inc.ftl	Fri Aug 13 14:59:05 2010 +0300
@@ -29,9 +29,31 @@
 At the start of preparation a new directory is created for the build and subst'ed to ``build.drive``. If a directory with this name already exists, it is renamed to have a current timestamp on the end.
 
 .. index::
-  single: How to prepare the build area?
+  single: How to prepare the build area
+
+How to prepare the build area
+-----------------------------
+
+Helium supports the creation of an environment based on a release store in a network drive. The main requirement from that release is to publish release metadata with the content.
+
+.. csv-table:: Ant properties to modify
+   :header: "Property", "Description", "Values"
 
-How to prepare the build area?
-------------------------------
+   ":hlm-p:`s60.grace.server`", "UNC path to network drive.", ""
+   ":hlm-p:`s60.grace.service`", "Service name.", ""
+   ":hlm-p:`s60.grace.product`", "Product name.", ""
+   ":hlm-p:`s60.grace.release`", "Regular expression to match release under the product directory.", ""
+   ":hlm-p:`s60.grace.revision`", "Regular expresion to match a new build revision", "e.g: (_\d+)?"
+   ":hlm-p:`s60.grace.cache`",
+   ":hlm-p:`s60.grace.checkmd5.enabled`",
+   ":hlm-p:`s60.grace.usetickler`", "Validate the release based on the tickler.", "true, false(default)"
 
-TODO
+Once configured you can invoke Helium:
+
+    > hlm -Dbuild.number=1 -Dbuild.drive=X: ido-update-build-area-grace
+
+    > dir X:
+    ...
+    ...
+
+You should then have the latest/mentioned release un-archived under the X: drive.
\ No newline at end of file