diff --git a/Documentation/Models/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook b/Documentation/Models/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook
index ace14cc..c47888c 100644
--- a/Documentation/Models/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook
+++ b/Documentation/Models/Docbook/Tcar-ug/Manuals/Production/identifying-goals.docbook
@@ -17,32 +17,32 @@
Before The CentOS Artwork Repository File
- System documentation manual exist, there was an
- emerging need to understand what each directory inside the
- growing directory layout was for, how they could be used and
- how they could be connected one another. At that moment, the
- directory layout was very unstable and explaining the whole
- idea behind it was not possible, there were too many changing
- concepts floating around which needed to be considered in the
- same changing way. So, to understand what was happening, the
- The CentOS Artwork Repository File
- System documentation manual was created.
+ System documentation manual would exist, there was
+ an emerging need to understand what each directory inside the
+ growing directory layout was for, how it could be used and
+ each directory could be connected one another. At that moment,
+ the directory layout was very unstable and explaining the
+ whole idea behind it was not possible, there were too many
+ changing concepts floating around which needed to be
+ considered in the same changing way. So, to understand what
+ was happening, the The CentOS Artwork Repository
+ File System documentation manual was created.
The The CentOS Artwork Repository File
System manual was conceived based on the idea of
- individually documenting each directory inside the repository
+ documenting each directory inside the repository individually
and, later, by considering all directory documentations
- together, it would be (hypothetically) possible to correct the
- whole idea through an improvement cycle that would consolidate
- the final idea we try to implement.
+ altogether, it would be (hypothetically) possible to correct
+ the whole idea through an improvement cycle that would
+ consolidate the final idea we were trying to implement.
Other documentation manuals can be based on reasons different
from those described above, however, no matter what those
- reasons be, it will be helpful to make yourself a clean idea
+ reasons are, it will be helpful to make yourself a clean idea
about what you are going to document exactly before putting
your hands on it.