diff --git a/Documentation/Models/Docbook/Tcar-ug/Scripts/Bash/render.docbook b/Documentation/Models/Docbook/Tcar-ug/Scripts/Bash/render.docbook
index 6509c63..4aab985 100644
--- a/Documentation/Models/Docbook/Tcar-ug/Scripts/Bash/render.docbook
+++ b/Documentation/Models/Docbook/Tcar-ug/Scripts/Bash/render.docbook
@@ -1,20 +1,18 @@
-<section id="scripts-bash-render">
+<refentry id="scripts-bash-render">
 
-    <title>Standardizing Rendition Tasks</title>
-    <indexterm type="specific-function">
-        <primary>render</primary>
-    </indexterm>
+    <refmeta>
+        <refentrytitle>render</refentrytitle>
+        <indexterm type="specific-function">
+            <primary>Standardize rendition tasks inside &TCAR;</primary>
+        </indexterm>
+    </refmeta>
 
-    <para>
-        The <function>render</function> functionality is the interface
-        the <command>centos-art.sh</command> script provides to
-        standardize the content production tasks inside the working
-        copy.
-    </para>
+    <refnamediv>
+        <refname>render</refname>
+        <refpurpose>Standardize rendition tasks inside &TCAR;</refpurpose>
+    </refnamediv>
 
-    <simplesect id="script-bash-render-syntax">
-    <title>Syntax</title>
-    <screen>centos-art render [OPTIONS] [DIRECTORY]</screen>
+    <refsynopsisdiv>
 
     <para>
         The <varname>DIRECTORY</varname> parameter specifies the
@@ -25,29 +23,82 @@
         parameter is not provided, the current directory path where
         the command was called from is used instead.
     </para>
-    </simplesect>
+    </refsynopsisdiv>
 
-    <simplesect id="script-bash-render-option">
-    <title>Options</title>
+    <refsection id="scripts-bash-render-description">
+    <title>Description</title>
 
     <para>
-        The <function>render</function> functionality accepts the
-        following options: 
+        Inside the working copy of &TCAR;, rendition tasks take place
+        inside renderable directories. The rendition itself is
+        performed through a serie of rendition flows named
+        base-rendition, post-rendition, last-rendition and
+        directory-specific rendition.
     </para>
 
-    <variablelist>
-    <varlistentry>
-    <term><option>--quiet</option></term>
-    <listitem>
     <para>
-        This option supresses all output messages except error
-        messages.  When this option is passed, all confirmation
-        requests are supressed and a possitive answer is assumed for
-        them, just as if the <option>--answer-yes</option> option
-        would have been provided.
+        Renderable directories are convenctional locations inside the
+        working copy where you can find source files, output files and
+        auxiliar files. Source files are used to produce output files.
+        Auxiliar files are used to modify the way output files are
+        produced from source files (e.g., to produce localized
+        output). Auxiliar files are optionals.
+    </para>
+    <para>
+        Renderable directories are made of several directories but
+        only the output dirctory path is passed to
+        <function>render</function> functionality as
+        <varname>DIRECTORY</varname> parameter in the command-line.
+        The directories related to source and auxiliar files are
+        automatically constructed based on a directory organization
+        convenction. This way, the <function>render</function>
+        functionality collects all the information it needs to work
+        with.
+    </para>
+
+    <para>
+        Inside the working copy, renderable directories are divided in
+        two categories in a way differences between them can be
+        preserved. These categories are named <quote>direct
+        production</quote> and <quote>theme production</quote>. These
+        categories provide the file organization convenction the
+        <function>render</function> functionality needs, to produce
+        content based on rendition flows.
+    </para>
+
+    <para>Direct Production </para>
+    <para>Theme Production</para>
+    <para>Base Rendition Flow</para>
+    <para>Post Rendition Flow</para>
+    <para>Last Rendition Flow</para>
+    <para>Directory-Specific Rendition Flow</para>
+    </refsection>
+
+    <refsection id="scripts-bash-render-environment">
+    <title>Function Specific Environment</title>
+    <para>
+        ...
+    </para>
+    </refsection>
+
+    <refsection id="scripts-bash-render-usage">
+    <title>Usage</title>
+    <para>
+        ...
+    </para>
+    </refsection>
+
+    <refsection id="scripts-bash-render-option">
+    <title>Options</title>
+
+    <para>
+        The <command>centos-art prepare</command> command accepts
+        common options described in <xref
+        linkend="scripts-bash-cli-commonoptions" /> and the following
+        specific options:
     </para>
-    </listitem>
-    </varlistentry>
+
+    <variablelist>
 
     <varlistentry>
     <term><option>--answer-yes</option></term>
@@ -158,65 +209,9 @@
     </listitem>
     </varlistentry>
     </variablelist>
-    </simplesect>
-
-    <simplesect id="script-bash-render-description">
-    <title>Description</title>
-
-    <para>
-        Inside the working copy of &TCAR;, rendition tasks take place
-        inside renderable directories. The rendition itself is
-        performed through a serie of rendition flows named
-        base-rendition, post-rendition, last-rendition and
-        directory-specific rendition.
-    </para>
-
-    <para>
-        Renderable directories are convenctional locations inside the
-        working copy where you can find source files, output files and
-        auxiliar files. Source files are used to produce output files.
-        Auxiliar files are used to modify the way output files are
-        produced from source files (e.g., to produce localized
-        output). Auxiliar files are optionals.
-    </para>
-    <para>
-        Renderable directories are made of several directories but
-        only the output dirctory path is passed to
-        <function>render</function> functionality as
-        <varname>DIRECTORY</varname> parameter in the command-line.
-        The directories related to source and auxiliar files are
-        automatically constructed based on a directory organization
-        convenction. This way, the <function>render</function>
-        functionality collects all the information it needs to work
-        with.
-    </para>
-
-    <para>
-        Inside the working copy, renderable directories are divided in
-        two categories in a way differences between them can be
-        preserved. These categories are named <quote>direct
-        production</quote> and <quote>theme production</quote>. These
-        categories provide the file organization convenction the
-        <function>render</function> functionality needs, to produce
-        content based on rendition flows.
-    </para>
-
-    <para>Direct Production </para>
-    <para>Theme Production</para>
-    <para>Base Rendition Flow</para>
-    <para>Post Rendition Flow</para>
-    <para>Last Rendition Flow</para>
-    <para>Directory-Specific Rendition Flow</para>
-    </simplesect>
-
-    <simplesect id="script-bash-render-environment">
-    <title>Function Specific Environment</title>
-    <para>
-        ...
-    </para>
-    </simplesect>
+    </refsection>
 
-    <simplesect id="scripts-bash-render-authors">
+    <refsection id="scripts-bash-render-authors">
     <title>Authors</title>
     <para>
         The following people have worked in the
@@ -229,9 +224,9 @@
     </para>
     </listitem>
     </itemizedlist>
-    </simplesect>
+    </refsection>
 
-    <simplesect id="scripts-bash-render-licence">
+    <refsection id="scripts-bash-render-licence">
     <title>License</title>
 
     <para>
@@ -258,6 +253,6 @@
         Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139,
         USA.
     </para>
-    </simplesect>
+    </refsection>
 
-</section>
+</refentry>