diff --git a/Manuals/RepoReference/en_US/Directories/trunk/Scripts/Functions/Help.texinfo b/Manuals/RepoReference/en_US/Directories/trunk/Scripts/Functions/Help.texinfo
index e95e69a..c5aac3f 100644
--- a/Manuals/RepoReference/en_US/Directories/trunk/Scripts/Functions/Help.texinfo
+++ b/Manuals/RepoReference/en_US/Directories/trunk/Scripts/Functions/Help.texinfo
@@ -274,10 +274,10 @@ that one set in the Info file, which might be something not desirable.
 Notice also that, the main purpose of using Texinfo as documentation
 backend to write documentation related to each repository directory,
 is the possibility it provides of producing Info files as output. This
-posibility is used by @command{centos-art.sh} script to refer places
-where documentation can be found when an error happens.  It is, let
-users to type a command immidiatly after errors, so they can know more
-about them. It is about creating a direct connection between the
+posibility is used by @command{centos-art.sh} script to build internal
+references where documentation can be found when errors happen.  It
+lets users to type a command immediatly after errors in order to know
+more about them. It is about creating a direct connection between the
 @command{centos-art.sh} script and the conceptual ideas behind it.
 
 @subheading Examples