diff --git a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Help.texinfo b/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Help.texinfo
index a61e88b..3ba6aee 100644
--- a/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Help.texinfo
+++ b/Manuals/Texinfo/Directories/trunk/Scripts/Functions/Help.texinfo
@@ -129,38 +129,48 @@ the repository.
 @end quotation
 
 Files inside the repository are not documented. The only exception to
-this rule are files under @file{trunk/Manual} directory, the place
+this rule are files under @file{trunk/Manuals} directory, the place
 where documentation source files are stored in. Inside this location
-you can refer @file{.texinfo} files for direct actions using the
-@code{help} functionality of @command{centos-art.sh} script. File
-actions, in this location, are also used to manage specific parts of
-the manual which have no association outside @file{trunk/Manual}
-directory (e.g., Preface, Introduction, etc.).
+you can refer files for direct actions using the @code{help}
+functionality of @command{centos-art.sh} script. File actions, in this
+location, are also used to manage specific parts of the manual which
+have no association outside @file{trunk/Manuals} directory (e.g.,
+Preface, Introduction, etc.).
 
-The manual structure (@pxref{Directories trunk Manual}) is supported
+@subsubsection The @samp{texinfo} backend
+
+The manual structure (@pxref{Directories trunk Manuals}) is supported
 by GNU Texinfo, a documentation system that can produce both online
 information and a printed manual from a single source. The @code{help}
 functionality is an interface you can use to control the source files
 in the manual structure.  
 
 The manual output is produced from Texinfo files and stored in
-@file{trunk/Manual} on different formats including Info, PDF, XHTML,
-XML and TXT.
-
-Whatever your prefered language be, you'll always edit documentation
-entries in English language and so will be the output produced from
-them, when you use the @code{help} functionality of
-@command{centos-art.sh} script. However, you can achieve the manual
-localization to your prefered language by applying the @code{locale}
+@file{trunk/Manuals/Texinfo} on different formats including Info, PDF,
+XHTML, XML and TXT.
+
+When the @samp{texinfo} backend is used, you'll always edit
+documentation entries in English language, no matter what your
+prefered language be. This way, the output produced from them will
+always be in English language. To achieve the manual localization in
+your prefered language you need to apply the @code{locale}
 functionality of @command{centos-art.sh} script (@pxref{Directories
 trunk Scripts Functions Locale}) to any of the XML-based English
-outputs supported by @command{centos-art.sh} script (e.g., XHTML and
-Docbook) to produce portable objects for your prefered language and
-the @code{render} functionality of @command{centos-art.sh} script
+outputs supported by @command{centos-art.sh} script (e.g., XHTML) to
+produce portable objects for your prefered language and the
+@code{render} functionality of @command{centos-art.sh} script
 (@pxref{Directories trunk Scripts Functions Render}) to produce the
 translated version of the output XHTML files taken in first place. The
-translated version is produced in the same format of the file taken
-as reference to build the portable objects. XHTML format in this case.
+translated version is produced in the same format of the file taken as
+reference to build the portable objects. XHTML format in this case.
+
+@subsubsection The @file{docbook} backend
+
+Not supported yet.
+
+@subsubsection The @file{linuxdoc} backend
+
+Not supported yet.
 
 @subheading Examples