diff --git a/Manuals/en/Html/Repository/repository_40.html b/Manuals/en/Html/Repository/repository_40.html index 06c92a7..d694946 100644 --- a/Manuals/en/Html/Repository/repository_40.html +++ b/Manuals/en/Html/Repository/repository_40.html @@ -320,7 +320,7 @@ script, just as the following command illustrates:

To have a well documented function helps user to understand how your function really works, and how it should be used. When no valid action is passed to a function, the `centos-art.sh' script uses -the function documentation entry as vehicle to let the user know which +the function documentation entry as vehicle to communicate which the valid functions are. When no documentation entry exists for a funtcion, that user has provided an invalid action for, the `centos-art.sh' script informs that no documentation entry exists diff --git a/Manuals/en/Info/Repository/repository.info.bz2 b/Manuals/en/Info/Repository/repository.info.bz2 index 07d2a2e..30e60f0 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 150097a..d128959 100644 --- a/Manuals/en/Plaintext/Repository/repository.txt +++ b/Manuals/en/Plaintext/Repository/repository.txt @@ -3045,11 +3045,11 @@ centos-art manual --edit=trunk/Scripts/Bash/Functions/Greet To have a well documented function helps user to understand how your function really works, and how it should be used. When no valid action is passed to a function, the `centos-art.sh' script uses the function -documentation entry as vehicle to let the user know which valid -functions are. When no documentation entry exists for a funtcion, that -user has provided an invalid action for, the `centos-art.sh' script -informs that no documentation entry exists for such function and -requests user to create it right at that time. +documentation entry as vehicle to communicate which the valid functions +are. When no documentation entry exists for a funtcion, that user has +provided an invalid action for, the `centos-art.sh' script informs that +no documentation entry exists for such function and requests user to +create it right at that time. Now that we have documented our function, it is time to translate its output messages to different languages. To translate specific diff --git a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi index 7680a50..8c4be91 100644 --- a/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi +++ b/Manuals/en/Texinfo/Repository/trunk/Scripts/Bash/Functions.texi @@ -256,7 +256,7 @@ centos-art manual --edit=trunk/Scripts/Bash/Functions/Greet To have a well documented function helps user to understand how your function really works, and how it should be used. When no valid action is passed to a function, the @file{centos-art.sh} script uses -the function documentation entry as vehicle to let the user know which +the function documentation entry as vehicle to communicate which the valid functions are. When no documentation entry exists for a funtcion, that user has provided an invalid action for, the @file{centos-art.sh} script informs that no documentation entry exists