diff --git a/Manuals/en/Html/Repository/repository_40.html b/Manuals/en/Html/Repository/repository_40.html
index a70b7e7..6be5263 100644
--- a/Manuals/en/Html/Repository/repository_40.html
+++ b/Manuals/en/Html/Repository/repository_40.html
@@ -625,9 +625,9 @@ verification <tt>`centos-art.sh'</tt> script makes with URL is granting
 that they begin with <samp>`https://projects.centos.org/svn/artwork'</samp>.
 </p>
 <p><code>cli_checkActionArguments</code> is called from
-<code>cli_getActionArguments</code> function and, probably, there is not
+<code>cli_getArguments</code> function and, probably, there is not
 other use for <code>cli_checkActionArguments</code> but to be called from
-<code>cli_getActionArguments</code> function.
+<code>cli_getArguments</code> function.
 </p>
 <p>Update <code>cli_checkActionArguments</code> function if you need to improve
 action value (<var>ACTIONVAL</var>) variable input validation.
@@ -768,21 +768,21 @@ function, and occasionally, farther redefined (by
 </p></dd></dl>
 
 <dl>
-<dt><u>Function:</u> <b>cli_getActionArguments</b><i> [$@]</i>
+<dt><u>Function:</u> <b>cli_getArguments</b><i> [$@]</i>
 <a name="IDX14"></a>
 </dt>
 <dd><p>Initialize function name (<var>FUNCNAM</var>), action name
 (<var>ACTIONNAM</var>), and action value (<var>ACTIONVAL</var>) global
 variables, using positional parameters passed in <var>$@</var> variable.
 </p>
-<p>The <code>cli_getActionsArguments</code> function is called from
-<code>cli.sh</code> function script, using <code>cli</code> function's positional
-parameters (i.e., the positional parameters passed as arguments in the
+<p>The <code>cli_getArguments</code> function is called from <code>cli.sh</code>
+function script, using <code>cli</code> function's positional parameters
+(i.e., the positional parameters passed as arguments in the
 command-line) as first function argument. 
 </p>
 <p>Once command-line positional parameters are accesible to
 <tt>`centos-art.sh'</tt> script execution evironment,
-<code>cli_getActionsArguments</code> uses regular expression to retrive
+<code>cli_getArguments</code> uses regular expression to retrive
 action variables from first and second argument. The first argument
 defines the value used as function name (<var>FUNCNAM</var>), and the
 second argument defines both values used as action name
@@ -804,14 +804,14 @@ action name acts on.
 </p>
 <p>Once action related variables (i.e., <var>FUNCNAM</var>, <var>ACTIONNAM</var>,
 and <var>ACTIONVAL</var>) are defined and validated,
-<code>cli_getActionsArguments</code> shifts the positional arguments to
-remove the first two arguments passed (i.e., those used to retrive
-action related variables) and redefine the arguments (<var>ARGUMENTS</var>)
-global variable with the new positional parameters information.
+<code>cli_getArguments</code> shifts the positional arguments to remove the
+first two arguments passed (i.e., those used to retrive action related
+variables) and redefine the arguments (<var>ARGUMENTS</var>) global
+variable with the new positional parameters information.
 </p></dd></dl>
 
 <dl>
-<dt><u>Function:</u> <b>cli_getActions</b>
+<dt><u>Function:</u> <b>cli_getFunctions</b>
 <a name="IDX15"></a>
 </dt>
 <dd><p>Initialize funtionalities supported by <tt>`centos-art.sh'</tt> script.
@@ -1112,8 +1112,10 @@ convenctions inside <tt>`centos-art.sh'</tt> script.
 what we are really changing is the way functions interpret repository
 file system organization. Notice that when we change a file name
 (e.g., a function name), it is necessary to update all files where
-such file name is placed on. This may require a massive substitution,
-each time we change name convenctions in the repository (see section <a href="repository_44.html#SEC234">trunk/Scripts/Bash/Functions/Path</a>, for more information).
+such file name is placed on. This may require a massive substitution
+inside the repository, each time we change name convenctions in the
+repository (see section <a href="repository_44.html#SEC234">trunk/Scripts/Bash/Functions/Path</a>, for more
+information).
 </p></dd></dl>
 
 <dl>
@@ -1122,10 +1124,12 @@ each time we change name convenctions in the repository (see section <a href="re
 </dt>
 <dd><p>Request repository status.
 </p>
-<p>This function requests the working copy using the <code>svn status</code>
-command and returns the first character in the output line, as
-described in <code>svn help status</code>, for the <var>LOCATION</var>
-specified.
+<p>This function requests the status of a <var>LOCATION</var> inside the
+working copy using the <code>svn status</code> command and returns the
+first character in the output line, just as described in <code>svn
+help status</code>. If <var>LOCATION</var> is not a regular file or a directory,
+inside the working copy, the <tt>`centos-art.sh'</tt> script prints a
+message and ends its execution.
 </p>
 <p>Use this function to perform verifications based a repository
 <var>LOCATION</var> status.
diff --git a/Manuals/en/Info/Repository/repository.info.bz2 b/Manuals/en/Info/Repository/repository.info.bz2
index 6c661bf..8ba0d2a 100644
Binary files a/Manuals/en/Info/Repository/repository.info.bz2 and b/Manuals/en/Info/Repository/repository.info.bz2 differ
diff --git a/Manuals/en/Plaintext/Repository/repository.txt b/Manuals/en/Plaintext/Repository/repository.txt
index 39f4e2c..31d2143 100644
--- a/Manuals/en/Plaintext/Repository/repository.txt
+++ b/Manuals/en/Plaintext/Repository/repository.txt
@@ -3311,10 +3311,10 @@ global functions you can use inside `centos-art.sh' script.
      with URL is granting that they begin with
      `https://projects.centos.org/svn/artwork'.
 
-     `cli_checkActionArguments' is called from `cli_getActionArguments'
+     `cli_checkActionArguments' is called from `cli_getArguments'
      function and, probably, there is not other use for
      `cli_checkActionArguments' but to be called from
-     `cli_getActionArguments' function.
+     `cli_getArguments' function.
 
      Update `cli_checkActionArguments' function if you need to improve
      action value (ACTIONVAL) variable input validation.
@@ -3431,23 +3431,23 @@ global functions you can use inside `centos-art.sh' script.
      function, and occasionally, farther redefined (by
      `cli_doParseArgumentsReDef') as far as it may be convenient.
 
- -- Function: cli_getActionArguments [$@]
+ -- Function: cli_getArguments [$@]
      Initialize function name (FUNCNAM), action name (ACTIONNAM), and
      action value (ACTIONVAL) global variables, using positional
      parameters passed in $@ variable.
 
-     The `cli_getActionsArguments' function is called from `cli.sh'
-     function script, using `cli' function's positional parameters
-     (i.e., the positional parameters passed as arguments in the
-     command-line) as first function argument.
+     The `cli_getArguments' function is called from `cli.sh' function
+     script, using `cli' function's positional parameters (i.e., the
+     positional parameters passed as arguments in the command-line) as
+     first function argument.
 
      Once command-line positional parameters are accesible to
-     `centos-art.sh' script execution evironment,
-     `cli_getActionsArguments' uses regular expression to retrive
-     action variables from first and second argument. The first argument
-     defines the value used as function name (FUNCNAM), and the second
-     argument defines both values used as action name (ACTIONNAM) and
-     action value (ACTIONVAL), respectively.
+     `centos-art.sh' script execution evironment, `cli_getArguments'
+     uses regular expression to retrive action variables from first and
+     second argument. The first argument defines the value used as
+     function name (FUNCNAM), and the second argument defines both
+     values used as action name (ACTIONNAM) and action value
+     (ACTIONVAL), respectively.
 
      The first argument is a word in lower case. This word specifies the
      name of the functionality you want to use (e.g., `render' to
@@ -3464,13 +3464,13 @@ global functions you can use inside `centos-art.sh' script.
      action name acts on.
 
      Once action related variables (i.e., FUNCNAM, ACTIONNAM, and
-     ACTIONVAL) are defined and validated, `cli_getActionsArguments'
-     shifts the positional arguments to remove the first two arguments
-     passed (i.e., those used to retrive action related variables) and
+     ACTIONVAL) are defined and validated, `cli_getArguments' shifts
+     the positional arguments to remove the first two arguments passed
+     (i.e., those used to retrive action related variables) and
      redefine the arguments (ARGUMENTS) global variable with the new
      positional parameters information.
 
- -- Function: cli_getActions
+ -- Function: cli_getFunctions
      Initialize funtionalities supported by `centos-art.sh' script.
 
      Functionalities supported by `centos-art.sh' script are organized
@@ -3738,16 +3738,19 @@ global functions you can use inside `centos-art.sh' script.
      repository file system organization. Notice that when we change a
      file name (e.g., a function name), it is necessary to update all
      files where such file name is placed on. This may require a
-     massive substitution, each time we change name convenctions in the
-     repository (*note trunk Scripts Bash Functions Path::, for more
-     information).
+     massive substitution inside the repository, each time we change
+     name convenctions in the repository (*note trunk Scripts Bash
+     Functions Path::, for more information).
 
  -- Function: cli_getRepoStatus [LOCATION]
      Request repository status.
 
-     This function requests the working copy using the `svn status'
-     command and returns the first character in the output line, as
-     described in `svn help status', for the LOCATION specified.
+     This function requests the status of a LOCATION inside the working
+     copy using the `svn status' command and returns the first
+     character in the output line, just as described in `svn help
+     status'. If LOCATION is not a regular file or a directory, inside
+     the working copy, the `centos-art.sh' script prints a message and
+     ends its execution.
 
      Use this function to perform verifications based a repository
      LOCATION status.
@@ -6279,24 +6282,24 @@ Index
 *****
 
 branches:                                      See 1.        (line  390)
-Common translation files:                      See 3.50.2.5. (line 5708)
-How to render brands' translation files:       See 3.52.3.   (line 6012)
-How to render fonts' translation files:        See 3.54.3.   (line 6085)
-How to render translation files:               See 3.50.3.   (line 5878)
-Metadata maintainance:                         See 3.45.2.   (line 4852)
-Specific translation files:                    See 3.50.2.6. (line 5733)
+Common translation files:                      See 3.50.2.5. (line 5711)
+How to render brands' translation files:       See 3.52.3.   (line 6015)
+How to render fonts' translation files:        See 3.54.3.   (line 6088)
+How to render translation files:               See 3.50.3.   (line 5881)
+Metadata maintainance:                         See 3.45.2.   (line 4855)
+Specific translation files:                    See 3.50.2.6. (line 5736)
 tags:                                          See 2.        (line  393)
-Template translation files:                    See 3.50.2.4. (line 5538)
-Translation brands file names:                 See 3.52.2.1. (line 5969)
-Translation configuration scripts:             See 3.50.2.8. (line 5767)
-Translation entries:                           See 3.50.2.1. (line 5354)
-Translation files:                             See 3.50.2.3. (line 5470)
-Translation markers:                           See 3.50.2.2. (line 5435)
-Translation paths:                             See 3.50.2.1. (line 5354)
+Template translation files:                    See 3.50.2.4. (line 5541)
+Translation brands file names:                 See 3.52.2.1. (line 5972)
+Translation configuration scripts:             See 3.50.2.8. (line 5770)
+Translation entries:                           See 3.50.2.1. (line 5357)
+Translation files:                             See 3.50.2.3. (line 5473)
+Translation markers:                           See 3.50.2.2. (line 5438)
+Translation paths:                             See 3.50.2.1. (line 5357)
 Translation pre-rendering configuration scripts:See 3.50.2.8.
-                                                             (line 5767)
-Translation rendering:                         See 3.50.2.7. (line 5756)
-Translation rendering default functionality:   See 3.50.2.9. (line 5853)
+                                                             (line 5770)
+Translation rendering:                         See 3.50.2.7. (line 5759)
+Translation rendering default functionality:   See 3.50.2.9. (line 5856)
 trunk:                                         See 3.        (line  396)
 trunk Identity:                                See 3.1.      (line  399)
 trunk Identity Brands:                         See 3.2.      (line  819)
@@ -6341,31 +6344,31 @@ trunk Manuals:                                 See 3.34.     (line 2579)
 trunk Scripts:                                 See 3.35.     (line 2633)
 trunk Scripts Bash:                            See 3.36.     (line 2657)
 trunk Scripts Bash Functions:                  See 3.37.     (line 2806)
-trunk Scripts Bash Functions Html:             See 3.38.     (line 3943)
-trunk Scripts Bash Functions Locale:           See 3.39.     (line 3964)
-trunk Scripts Bash Functions Manual:           See 3.40.     (line 4044)
-trunk Scripts Bash Functions Path:             See 3.41.     (line 4065)
-trunk Scripts Bash Functions Render:           See 3.42.     (line 4467)
-trunk Scripts Bash Functions Render Config:    See 3.43.     (line 4488)
-trunk Scripts Bash Functions Shell:            See 3.44.     (line 4666)
-trunk Scripts Bash Functions Svg:              See 3.45.     (line 4834)
-trunk Scripts Bash Functions Verify:           See 3.46.     (line 5022)
-trunk Scripts Bash Locale:                     See 3.47.     (line 5238)
-trunk Scripts Perl:                            See 3.48.     (line 5267)
-trunk Scripts Python:                          See 3.49.     (line 5284)
-trunk Translations:                            See 3.50.     (line 5305)
-trunk Translations Identity:                   See 3.51.     (line 5907)
-trunk Translations Identity Brands:            See 3.52.     (line 5928)
-trunk Translations Identity Brands Tpl:        See 3.53.     (line 6023)
-trunk Translations Identity Fonts:             See 3.54.     (line 6038)
-trunk Translations Identity Models:            See 3.55.     (line 6101)
-trunk Translations Identity Release:           See 3.56.     (line 6116)
-trunk Translations Identity Themes:            See 3.57.     (line 6131)
-trunk Translations Identity Themes Backgrounds:See 3.58.     (line 6146)
+trunk Scripts Bash Functions Html:             See 3.38.     (line 3946)
+trunk Scripts Bash Functions Locale:           See 3.39.     (line 3967)
+trunk Scripts Bash Functions Manual:           See 3.40.     (line 4047)
+trunk Scripts Bash Functions Path:             See 3.41.     (line 4068)
+trunk Scripts Bash Functions Render:           See 3.42.     (line 4470)
+trunk Scripts Bash Functions Render Config:    See 3.43.     (line 4491)
+trunk Scripts Bash Functions Shell:            See 3.44.     (line 4669)
+trunk Scripts Bash Functions Svg:              See 3.45.     (line 4837)
+trunk Scripts Bash Functions Verify:           See 3.46.     (line 5025)
+trunk Scripts Bash Locale:                     See 3.47.     (line 5241)
+trunk Scripts Perl:                            See 3.48.     (line 5270)
+trunk Scripts Python:                          See 3.49.     (line 5287)
+trunk Translations:                            See 3.50.     (line 5308)
+trunk Translations Identity:                   See 3.51.     (line 5910)
+trunk Translations Identity Brands:            See 3.52.     (line 5931)
+trunk Translations Identity Brands Tpl:        See 3.53.     (line 6026)
+trunk Translations Identity Fonts:             See 3.54.     (line 6041)
+trunk Translations Identity Models:            See 3.55.     (line 6104)
+trunk Translations Identity Release:           See 3.56.     (line 6119)
+trunk Translations Identity Themes:            See 3.57.     (line 6134)
+trunk Translations Identity Themes Backgrounds:See 3.58.     (line 6149)
 trunk Translations Identity Themes Distro Anaconda Progress:See 3.59.
-                                                             (line 6167)
-trunk Translations Identity Widgets:           See 3.60.     (line 6260)
-Unused definitions:                            See 3.45.2.1. (line 4959)
+                                                             (line 6170)
+trunk Translations Identity Widgets:           See 3.60.     (line 6263)
+Unused definitions:                            See 3.45.2.1. (line 4962)
 List of Figures
 ***************
 
diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi
index 7cb08db..b23c8e9 100644
--- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi
+++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi
@@ -538,9 +538,9 @@ verification @file{centos-art.sh} script makes with URL is granting
 that they begin with @samp{https://projects.centos.org/svn/artwork}.
 
 @code{cli_checkActionArguments} is called from
-@code{cli_getActionArguments} function and, probably, there is not
+@code{cli_getArguments} function and, probably, there is not
 other use for @code{cli_checkActionArguments} but to be called from
-@code{cli_getActionArguments} function.
+@code{cli_getArguments} function.
 
 Update @code{cli_checkActionArguments} function if you need to improve
 action value (@var{ACTIONVAL}) variable input validation.
@@ -664,20 +664,20 @@ function, and occasionally, farther redefined (by
 @code{cli_doParseArgumentsReDef}) as far as it may be convenient.
 @end defun
 
-@defun cli_getActionArguments [$@@]
+@defun cli_getArguments [$@@]
 
 Initialize function name (@var{FUNCNAM}), action name
 (@var{ACTIONNAM}), and action value (@var{ACTIONVAL}) global
 variables, using positional parameters passed in @var{$@@} variable.
 
-The @code{cli_getActionsArguments} function is called from
-@code{cli.sh} function script, using @code{cli} function's positional
-parameters (i.e., the positional parameters passed as arguments in the
+The @code{cli_getArguments} function is called from @code{cli.sh}
+function script, using @code{cli} function's positional parameters
+(i.e., the positional parameters passed as arguments in the
 command-line) as first function argument. 
 
 Once command-line positional parameters are accesible to
 @file{centos-art.sh} script execution evironment,
-@code{cli_getActionsArguments} uses regular expression to retrive
+@code{cli_getArguments} uses regular expression to retrive
 action variables from first and second argument. The first argument
 defines the value used as function name (@var{FUNCNAM}), and the
 second argument defines both values used as action name
@@ -699,13 +699,13 @@ action name acts on.
 
 Once action related variables (i.e., @var{FUNCNAM}, @var{ACTIONNAM},
 and @var{ACTIONVAL}) are defined and validated,
-@code{cli_getActionsArguments} shifts the positional arguments to
-remove the first two arguments passed (i.e., those used to retrive
-action related variables) and redefine the arguments (@var{ARGUMENTS})
-global variable with the new positional parameters information.
+@code{cli_getArguments} shifts the positional arguments to remove the
+first two arguments passed (i.e., those used to retrive action related
+variables) and redefine the arguments (@var{ARGUMENTS}) global
+variable with the new positional parameters information.
 @end defun
 
-@defun cli_getActions
+@defun cli_getFunctions
 Initialize funtionalities supported by @file{centos-art.sh} script.
 
 Functionalities supported by @file{centos-art.sh} script are organized
@@ -985,18 +985,21 @@ When we change file name convenctions inside @code{cli_getRepoName}
 what we are really changing is the way functions interpret repository
 file system organization. Notice that when we change a file name
 (e.g., a function name), it is necessary to update all files where
-such file name is placed on. This may require a massive substitution,
-each time we change name convenctions in the repository (@pxref{trunk
-Scripts Bash Functions Path}, for more information).
+such file name is placed on. This may require a massive substitution
+inside the repository, each time we change name convenctions in the
+repository (@pxref{trunk Scripts Bash Functions Path}, for more
+information).
 @end defun
 
 @defun cli_getRepoStatus [LOCATION]
 Request repository status.
 
-This function requests the working copy using the @command{svn status}
-command and returns the first character in the output line, as
-described in @command{svn help status}, for the @var{LOCATION}
-specified.
+This function requests the status of a @var{LOCATION} inside the
+working copy using the @command{svn status} command and returns the
+first character in the output line, just as described in @command{svn
+help status}. If @var{LOCATION} is not a regular file or a directory,
+inside the working copy, the @file{centos-art.sh} script prints a
+message and ends its execution.
 
 Use this function to perform verifications based a repository
 @var{LOCATION} status.