diff --git a/Manuals/Tcar-ug/Manuals/Production/identifying-title.docbook b/Manuals/Tcar-ug/Manuals/Production/identifying-title.docbook
index 9746d03..3befd12 100644
--- a/Manuals/Tcar-ug/Manuals/Production/identifying-title.docbook
+++ b/Manuals/Tcar-ug/Manuals/Production/identifying-title.docbook
@@ -3,24 +3,19 @@
Once you've make yourself an clean idea of what the
documentation manual is for and the needs behind, it is time
- for to define the manual's title and the manual's directory
- name. Both manuals' title and manual's directory name
- describe what the documentation manual is about. The manual's
- title is used inside the documentation and the manual's
- directory name is used to store the related source files
- inside the repository. As convenction, manual's title is a
- few words phrase while manual's directory name is the
+ for you to define the manual's title and the manual's
+ directory name. Both manuals' title and manual's directory
+ name describe what the documentation manual is about. The
+ manual's title is used inside the documentation and the
+ manual's directory name is used to store the related source
+ files inside the repository. As convenction, manual's title is
+ a few words phrase while manual's directory name is the
abbreviation of that phrase set as manual's title.
- Following with our example, the documentation manual was
- initially titled The CentOS Artwork Repository File
- System
but that name was too long to remain that way,
- so it was abbreviated soon into TCAR-FS
which
- is less descriptive but easier to remember and doesn't need to
- be translated into other languages. The related manual's
- directory for it would be
+ Following with our example, the manual's title has been
+ already mentioned and its directory was set to
Tcar-fs
in order to comply
with the file name convenctions described at .