diff --git a/Manuals/Repository/Docbook/Identity.docbook b/Manuals/Repository/Docbook/Identity.docbook
index 39602b1..34f5212 100644
--- a/Manuals/Repository/Docbook/Identity.docbook
+++ b/Manuals/Repository/Docbook/Identity.docbook
@@ -1,4 +1,4 @@
-<part>
+<part id="identity">
<title>Visual Identity</title>
@@ -6,131 +6,10 @@
<para>...</para>
</partintro>
- <chapter>
- <title>The CentOS Project</title>
- <para>...</para>
-
- <sect1>
- <title>Mission</title>
- <para>...</para>
- </sect1>
-
- <sect1>
- <title>Special Interest Groups (SIGs)</title>
- <para>...</para>
- <sect2>
- <title>The CentOS Artwork SIG</title>
- <para>
- Inside the CentOS Project, The CentOS Artwork SIG
- produces The CentOS Project corporate visual
- identity through image files, mainly. On the
- other hand, The CentOS Project produces The CentOS
- Distribution and uses the image files produced by
- The CentOS Artwork SIG to cover the artwork needs
- inside The CentOS Distirbution and other corporate
- visual manifestations like web sites and
- showrooms.
- </para>
-
- <para>
- The contents produced by The CentOS Artwork SIG
- (e.g., graphic desings, documentaion, scripts and
- translations) are copyright of The CentOS Artwork
- SIG and the content produced by The CentOS Project
- (e.g., The CentOS Distribution) is copyright of
- The CentOS Project.
- </para>
-
- <para>
- The content produced by The CentOS Project and The
- CentOS Artwork SIG are both released as a GPL work
- in order for them to integrate one another.
- </para>
- </sect2>
- </sect1>
-
- </chapter>
-
- <chapter>
- <title>The CentOS Logo</title>
- <para>...</para>
-
- <sect1 id="identity-logo-intro">
-
- <title>Introduction</title>
-
- <para>
- The CentOS Logo is the main visual manifestaion of The
- CentOS Project. The CentOS Project uses The CentOS Logo to
- connect all its visual manifestions (e.g., GNU/Linux
- Distributions, Websites, Stationery, etc.) and, this way,
- it provides recognition among other similar projects
- available on the Internet.
- </para>
-
- <para>
- Both The CentOS Logo and all the visual manifestations
- that derivate from it are available for you to study and
- propose improvement around a good citizen's will at The
- CentOS Community environment, but you are not allowed to
- redistribute them elsewhere, without the given permission
- of The CentOS Project.
- </para>
-
- <para>
- If you need to redistribute either The CentOS Logo or any
- visual manifestation derived from it, write your
- intentions to the The CentOS Developers mailing list
- (<ulink
- url="mailto:centos-devel@centos.org">centos-devel@centos.org</ulink>).
- </para>
-
- </sect1>
-
- <sect1>
- <title>...</title>
- <para>...</para>
- </sect1>
-
- </chapter>
-
- <chapter>
-
- <title>The CentOS Distribution</title>
- <para>...</para>
-
- <sect1>
- <title>Release Schema</title>
- <para>...</para>
- </sect1>
-
- <sect1>
- <title>...</title>
- <para>...</para>
- </sect1>
-
- </chapter>
-
- <chapter>
- <title>The CentOS Web</title>
- <para>...</para>
-
- <sect1>
- <title>...</title>
- <para>...</para>
- </sect1>
-
- </chapter>
-
- <chapter>
- <title>The CentOS Showroom</title>
- <para>...</para>
-
- <sect1>
- <title>...</title>
- <para>...</para>
- </sect1>
-
- </chapter>
+ &identity-project;
+ &identity-logo;
+ &identity-distribution;
+ &identity-web;
+ &identity-showroom;
</part>
diff --git a/Manuals/Repository/Docbook/Identity.ent b/Manuals/Repository/Docbook/Identity.ent
index 7be8037..72e19e3 100644
--- a/Manuals/Repository/Docbook/Identity.ent
+++ b/Manuals/Repository/Docbook/Identity.ent
@@ -1 +1,8 @@
-<!ENTITY identity SYSTEM "Identity.docbook">
+<!ENTITY identity SYSTEM "Identity.docbook">
+<!ENTITY identity-project SYSTEM "Identity/Project.docbook">
+<!ENTITY identity-project-mission SYSTEM "Identity/Project/mission.docbook">
+<!ENTITY identity-project-sigs SYSTEM "Identity/Project/sigs.docbook">
+<!ENTITY identity-logo SYSTEM "Identity/Logo.docbook">
+<!ENTITY identity-distribution SYSTEM "Identity/Distribution.docbook">
+<!ENTITY identity-showroom SYSTEM "Identity/Showroom.docbook">
+<!ENTITY identity-web SYSTEM "Identity/Web.docbook">
diff --git a/Manuals/Repository/Docbook/Introduction.docbook b/Manuals/Repository/Docbook/Introduction.docbook
index e6178ab..2c738cc 100644
--- a/Manuals/Repository/Docbook/Introduction.docbook
+++ b/Manuals/Repository/Docbook/Introduction.docbook
@@ -5,33 +5,34 @@
<partintro>
<para>
- Welcome to <emphasis>The CentOS Artwork Repository
- Manual</emphasis>.
+ Welcome to <citetitle>The CentOS Artwork Repository User's
+ Guide</citetitle>.
</para>
<para>
- The CentOS Artwork Repository Manual describes how The CentOS
- Project corporate visual identity is organized and produced
- inside the CentOS Artwork Repository (<ulink
- url="https://projects.centos.org/svn/artwork/" />). If you
- are looking for a comprehensive, task-oriented guide for
+ The CentOS Artwork Repository User's Guide describes how The
+ CentOS Project corporate visual identity is organized and
+ produced inside <ulink
+ url="https://projects.centos.org/svn/artwork/">The CentOS
+ Artwork Repository</ulink>. If you are looking for a
+ comprehensive, task-oriented guide for
understanding how The CentOS Project corporate visual identity
is produced, this is the manual for you.
</para>
<para>
- This guide assumes you have a basic understanding of The
+ This manual assumes you have a basic understanding of The
CentOS Distribution. If you need help with CentOS, refer to
- the help page on The CentOS Wiki (<ulink
- url="http://wiki.centos.org/Help" />) for a list of different
- places you can find help.
+ the help page on <ulink url="http://wiki.centos.org/Help">The
+ CentOS Wiki</ulink> for a list of different places you can
+ find help.
</para>
</partintro>
- &intro-history;
- &intro-copying;
&intro-docconvs;
+ &intro-copying;
+ &intro-history;
&intro-usage;
&intro-feedback;
diff --git a/Manuals/Repository/Docbook/Introduction.ent b/Manuals/Repository/Docbook/Introduction.ent
index b63ae4a..b6449a7 100644
--- a/Manuals/Repository/Docbook/Introduction.ent
+++ b/Manuals/Repository/Docbook/Introduction.ent
@@ -1,6 +1,7 @@
-<!ENTITY intro SYSTEM "Introduction.docbook">
-<!ENTITY intro-history SYSTEM "Introduction/History.docbook">
-<!ENTITY intro-copying SYSTEM "Introduction/Copying.docbook">
-<!ENTITY intro-docconvs SYSTEM "Introduction/Docconvs.docbook">
-<!ENTITY intro-usage SYSTEM "Introduction/Repoconvs.docbook">
-<!ENTITY intro-feedback SYSTEM "Introduction/Feedback.docbook">
+<!ENTITY intro SYSTEM "Introduction.docbook">
+<!ENTITY intro-history SYSTEM "Introduction/History.docbook">
+<!ENTITY intro-copying SYSTEM "Introduction/Copying.docbook">
+<!ENTITY intro-copying-preamble SYSTEM "Introduction/Copying/preamble.docbook">
+<!ENTITY intro-docconvs SYSTEM "Introduction/Docconvs.docbook">
+<!ENTITY intro-usage SYSTEM "Introduction/Repoconvs.docbook">
+<!ENTITY intro-feedback SYSTEM "Introduction/Feedback.docbook">
diff --git a/Manuals/Repository/Docbook/Introduction/Copying.docbook b/Manuals/Repository/Docbook/Introduction/Copying.docbook
index b51a071..2420c5d 100644
--- a/Manuals/Repository/Docbook/Introduction/Copying.docbook
+++ b/Manuals/Repository/Docbook/Introduction/Copying.docbook
@@ -1,6 +1,6 @@
<chapter id="intro-copying" xreflabel="Copying conditions">
- <title>Copying Conditions</title>
+ <title>Repository Copying Conditions</title>
<para>
Copyright © 2009, 2010, 2011 The CentOS Artwork SIG
@@ -11,77 +11,6 @@
of this license document, but changing it is not allowed.
</para>
- <simplesect id="intro-copying-preamble" xreflabel="Preamble">
+ &intro-copying-preamble;
- <title>Preamble</title>
-
- <para>
- The CentOS Artwork Repository organizes files in a very
- specific way to implement The CentOS Project corporate visual
- identity. This very specific organization of files must be
- considered part of <command>centos-art.sh</command> script, a
- bash script that automate most of the frequent tasks inside
- the repository.
- </para>
-
- <para>
- The <command>centos-art.sh</command> script and the
- organization of files it needs to work are not in the public
- domain; they are copyrighted and there are restrictions on
- their distribution, but these restrictions are designed to
- permit everything that a good cooperating citizen would want
- to do. What is not allowed is to try to prevent others from
- further sharing any version of this program that they might
- get from you.
- </para>
-
- <para>
- Specifically, we want to make sure that you have the right to
- give away copies of <command>centos-art.sh</command> script
- and the organization of files it needs to work, that you
- receive source code or else can get it if you want it, that
- you can change this program or use pieces of it in new free
- programs, and that you know you can do these things.
- </para>
-
- <para>
- To make sure that everyone has such rights, we have to forbid
- you to deprive anyone else of these rights. For example, if
- you distribute copies of the <command>centos-art.sh</command>
- script, you must give the recipients all the rights that you
- have. You must make sure that they, too, receive or can get
- the source code. And you must tell them their rights.
- </para>
-
- <para>
- Also, for our own protection, we must make certain that
- everyone finds out that there is no warranty for the
- <command>centos-art.sh</command> script. If this program is
- modified by someone else and passed on, we want their
- recipients to know that what they have is not what we
- distributed, so that any problems introduced by others will
- not reflect on our reputation.
- </para>
-
- <para>
- The <command>centos-art.sh</command> script is released as a
- GPL work. Individual packages used by
- <command>centos-art.sh</command> script include their own
- licenses and the <command>centos-art.sh</command> script
- license applies to all packages that it does not clash with.
- If there is a clash between the
- <command>centos-art.sh</command> script license and individual
- package licenses, the individual package license applies
- instead.
- </para>
-
- <para>
- The precise conditions of the license for the
- <command>centos-art.sh</command> script are found in the <xref
- linkend="licenses-gpl" />. This manual specifically is covered
- by the <xref linkend="licenses-gfdl" />.
- </para>
-
- </simplesect>
-
</chapter>
diff --git a/Manuals/Repository/Docbook/Introduction/Docconvs.docbook b/Manuals/Repository/Docbook/Introduction/Docconvs.docbook
index 8cbaf70..9efcdb9 100644
--- a/Manuals/Repository/Docbook/Introduction/Docconvs.docbook
+++ b/Manuals/Repository/Docbook/Introduction/Docconvs.docbook
@@ -2,115 +2,225 @@
<title>Document Convenctions</title>
- <para>In this manual the personal pronoun <emphasis>we</emphasis>
- is used to repesent <emphasis>The CentOS Artwork SIG</emphasis>,
- the group of persons that build The CentOS Project corporate
- visual identity through the CentOS Artwork Repository.</para>
-
- <para>In this manual, certain words are represented in different
- fonts, typefaces, sizes, and weights. This highlighting is
- systematic; different words are represented in the same style to
- indicate their inclusion in a specific category. The types of
- words that are represented this way include the following:</para>
-
- <glosslist>
- <glossentry>
- <glossterm><command>command</command></glossterm>
- <glossdef>
- <para> Linux commands (and other operating system
- commands, when used) are represented this way. This
- style should indicate to you that you can type the
- word or phrase on the command line and press Enter to
- invoke a command. Sometimes a command contains words
- that would be displayed in a different style on their
- own (such as file names). In these cases, they are
- considered to be part of the command, so the entire
- phrase is displayed as a command. For example:</para>
-
- <para>Use the <command>centos-art identity
- --render='path/to/dir'</command> command to produce
- contents inside the <filename
- class="directory">trunk/Identity</filename> directory
- structure.</para>
+ <para>
+ In this manual, certain words are represented in different
+ fonts, typefaces, sizes, and weights. This highlighting is
+ systematic; different words are represented in the same style
+ to indicate their inclusion in a specific category. The types
+ of words that are represented this way include the
+ following:
+ </para>
+
+ <variablelist>
+ <varlistentry>
+ <term><command>command</command></term>
+ <listitem>
+ <para>
+ Linux commands (and other operating system
+ commands, when used) are represented this way.
+ This style should indicate to you that you can
+ type the word or phrase on the command line and
+ press Enter to invoke a command. Sometimes a
+ command contains words that would be displayed in
+ a different style on their own (such as file
+ names). In these cases, they are considered to be
+ part of the command, so the entire phrase is
+ displayed as a command.
+ </para>
+ <para>
+ Example:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use the <command>centos-art render <filename
+ class="directory">trunk/Manuals/Repository/Docbook</filename>
+ --filter="repository"</command> command to produce
+ the CentOS Artwork Repository User's Guide.
+ </para>
+ </listitem>
+ </itemizedlist>
- </glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm><filename>file name</filename></glossterm>
- <glossdef>
- <para>File names, directory names, paths, and RPM
- package names are represented this way. This style
- indicates that a particular file or directory exists
- with that name on your system. Examples:</para>
-
- <para>The <filename>init.sh</filename> file in
- <filename
- class="directory">trunk/Scripts/Bash/Cli/</filename>
- directory is the initialization script, written in
- Bash, used to automate most of tasks in the
- repository.</para>
-
- <para>The <command>centos-art</command> command uses
- the <package>ImageMagick</package> RPM package to
- convert images from PNG format to other
- formats.</para>
-
- </glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm><keycap>key</keycap></glossterm>
- <glossdef>
- <para> A key on the keyboard is shown in this style.
- For example:</para>
-
- <para>To use <keycap>TAB</keycap> completion to list
- particular files in a directory, type @command{ls},
- then a character, and finally the Tab key. Your
- terminal displays the list of files in the working
- directory that begin with that character.</para>
- </glossdef>
- </glossentry>
-
- <glossentry>
- <glossterm><keycombo action="simul"><keycap>key-combination</keycap></keycombo></glossterm>
- <glossdef>
- <para>A combination of keystrokes is represented in
- this way. For example:</para>
-
- <para>The <keycombo
- action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Backspace</keycap></keycombo>
- key combination exits your graphical session and
- returns you to the graphical login screen or the
- console.</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><filename>file name</filename></term>
+ <listitem>
+ <para>
+ File names, directory names, paths, and RPM
+ package names are represented this way. This style
+ indicates that a particular file or directory
+ exists with that name on your system.
+ </para>
+ <para>
+ Example:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ The <filename>init.sh</filename> file in <filename
+ class="directory">trunk/Scripts/Bash/Cli/</filename>
+ directory is the initialization script, written in
+ Bash, used to automate most of tasks in the
+ repository.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The <command>centos-art</command> command uses the
+ <package>ImageMagick</package> RPM package to
+ convert images from PNG format to other
+ formats.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><keycap>key</keycap></term>
+ <listitem>
+ <para>
+ A key on the keyboard is shown in this style.
+ </para>
+ <para>
+ Example:
+ </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>To use <keycap>Tab</keycap> completion to list
+ particular files in a directory, type
+ <command>ls</command>, then a character, and finally
+ the <keycap>Tab</keycap> key. Your terminal displays
+ the list of files in the working directory that begin
+ with that character.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><keycombo action="simul"><keycap>key</keycap><keycap>combination</keycap></keycombo></term>
+ <listitem>
+ <para>
+ A combination of keystrokes is represented in this
+ way.
+ </para>
+ <para>
+ Example:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ The <keycombo
+ action="simul"><keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Backspace</keycap></keycombo>
+ key combination exits your graphical session and
+ returns you to the graphical login screen or the
+ console.
+ </para>
+ </listitem>
+ </itemizedlist>
- </glossdef>
+ </listitem>
- </glossentry>
-
- <glossentry>
- <glossterm><computeroutput>computer output</computeroutput></glossterm>
- <glossdef>
- <para> Text in this style indicates text displayed to a
- shell prompt such as error messages and responses to
- commands. For example:</para>
+ </varlistentry>
- <para>The <command>ls</command> command displays the
- contents of a directory. For example:
+ <varlistentry>
+ <term><computeroutput>computer output</computeroutput></term>
+ <listitem>
+ <para>
+ Text in this style indicates text displayed to a shell
+ prompt such as error messages and responses to
+ commands. For example, the <command>ls</command>
+ command displays the contents of a directory using
+ this style:
+ </para>
<programlisting>
-Config help_renameEntry.sh
-help_copyEntry.sh help_restoreCrossReferences.sh
-help_deleteCrossReferences.sh help_searchIndex.sh
+render_doTranslation.sh render_getDirTemplate.sh render_doBaseActions.sh
+render_getConfigOption.sh render_getOptions.sh render_doThemeActions.sh
+render_getDirOutput.sh render.sh
</programlisting>
- The output returned in response to the command (in this
- case, the contents of the directory) is shown in this
- style.</para>
- </glossdef>
- </glossentry>
- </glosslist>
+ <para>
+ The output returned in response to the command (in
+ this case, the contents of the directory) is shown in
+ this style.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><prompt>prompt</prompt></term>
+ <listitem>
+ <para>
+ A prompt, which is a computer's way of signifying that it
+ is ready for you to input something, is shown in this
+ style. Examples:
+ <itemizedlist>
+ <listitem>
+ <para>
+ <prompt>$</prompt>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <prompt>#</prompt>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <prompt>[centos@projects centos]$</prompt>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <prompt>projects login:</prompt>
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><userinput>user input</userinput></term>
+ <listitem>
+ <para>
+ Text that the user types, either on the command line or
+ into a text box on a GUI screen, is displayed in this
+ style. In the following example,
+ <userinput>text</userinput> is displayed in this style: To
+ boot your system into the text based installation program,
+ you must type in the <userinput>text</userinput> command
+ at the <prompt>boot:</prompt> prompt.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><replaceable>replaceable</replaceable></term>
+ <listitem>
+ <para>
+ Text used in examples that is meant to be replaced with
+ data provided by the user is displayed in this style. In
+ the following example,
+ <replaceable>version-number</replaceable> is displayed in
+ this style: The directory for the kernel source is
+ <filename
+ class="directory">/usr/src/kernels/<replaceable>version-number</replaceable>/</filename>,
+ where <replaceable>version-number</replaceable> is the
+ version and type of kernel installed on this system.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
<para>Additionally, we use several different strategies to draw
your attention to certain pieces of information. In order of
diff --git a/Manuals/Repository/Docbook/Introduction/History.docbook b/Manuals/Repository/Docbook/Introduction/History.docbook
index 3b362bc..56f5ca4 100644
--- a/Manuals/Repository/Docbook/Introduction/History.docbook
+++ b/Manuals/Repository/Docbook/Introduction/History.docbook
@@ -1,14 +1,15 @@
<chapter id="intro-history" xreflabel="History">
- <title>History</title>
+ <title>Repository History</title>
<para>
- The CentOS Artwork Repository started during a discussion
- about how to automate the slide images of Anaconda, at CentOS
- Developers mailing list (<ulink
+ The CentOS Artwork Repository started at CentOS Developers
+ mailing list (<ulink
url="mailto:centos-devel@centos.org">centos-devel@centos.org</ulink>)
- around 2008. In such discussion, Ralph Angenendt rose up his
- hand to ask —Do you have something to show?—.
+ around 2008, on a discussion about how to automate slide
+ images used by Anaconda. In such discussion, Ralph Angenendt
+ rose up his hand to ask —Do you have something to
+ show?—.
</para>
<para>
diff --git a/Manuals/Repository/Docbook/Introduction/Repoconvs.docbook b/Manuals/Repository/Docbook/Introduction/Repoconvs.docbook
index 7b8258c..25e57de 100644
--- a/Manuals/Repository/Docbook/Introduction/Repoconvs.docbook
+++ b/Manuals/Repository/Docbook/Introduction/Repoconvs.docbook
@@ -1,37 +1,46 @@
-<chapter id="intro-usage" xreflabel="Usage convenctions">
+<chapter id="intro-usage">
<title>Repository Convenctions</title>
- <para>The CentOS Artwork Repository is supported by Subversion
- (http://subversion.tigris.org/), a version control system which
- allows you to keep old versions of files and directories (usually
- source code), keep a log of who, when, and why changes occurred,
- etc., like CVS, RCS or SCCS.</para>
+ <para>
+ The CentOS Artwork Repository is supported by <ulink
+ url="http://subversion.tigris.org/">Subversion</ulink>, a
+ version control system which allows you to keep old versions
+ of files and directories (usually source code), keep a log of
+ who, when, and why changes occurred, etc., like CVS, RCS or
+ SCCS.
+ </para>
- <para>When using Subversion there is one "source repository" and
- many "working copies" of that source repository. The working
- copies are independent one another, can be distributed all around
- the world and provide a local place for designers, documentors,
- translators and programmers to perform their work in a
- descentralized way. The source repository, on the other hand,
- provides a central place for all independent working copies to
- interchange data and provides the information required to permit
- extracting previous versions of files at any time.</para>
+ <para>
+ When using Subversion there is one "source repository" and
+ many "working copies" of that source repository. The working
+ copies are independent one another, can be distributed all
+ around the world and provide a local place for designers,
+ documentors, translators and programmers to perform their work
+ in a descentralized way. The source repository, on the other
+ hand, provides a central place for all independent working
+ copies to interchange data and provides the information
+ required to permit extracting previous versions of files at
+ any time.
+ </para>
- <sect1 id="repo-usage-policy" xreflabel="Policy">
+ <sect1 id="repo-usage-policy">
<title>Policy</title>
- <para>The CentOS Artwork Repository is a collaborative tool
- that anyone can have access to. However, changing that tool in
- any form is something that should be requested in the CentOS
- Developers mailing list (centos-devel@centos.org). Generally,
- people download working copies from CentOS Artwork Repository,
- study the repository organization, make some changes in their
- working copies, make some tests to verify such changes do work
- the way expected and finally request access to commit them up
- to the CentOS Artwork Repository (i.e., the source repository)
- for others to benefit from them.</para>
+ <para>
+ The CentOS Artwork Repository is a collaborative tool that
+ anyone can have access to. However, changing that tool in
+ any form is something that should be requested in the
+ CentOS Developers mailing list (centos-devel@centos.org).
+ Generally, people download working copies from CentOS
+ Artwork Repository, study the repository organization,
+ make some changes in their working copies, make some tests
+ to verify such changes do work the way expected and
+ finally request access to commit them up to the CentOS
+ Artwork Repository (i.e., the source repository) for
+ others to benefit from them.
+ </para>
<para>Once you've received access to commit your changes,
there is no need for you to request permission again to commit
@@ -72,7 +81,7 @@
</sect1>
- <sect1 id="intro-usage-worklines" xreflabel="Worklines">
+ <sect1 id="intro-usage-worklines">
<title>Work Lines</title>
@@ -129,7 +138,7 @@
</sect1>
- <sect1 id="intro-usage-conbdirs" xreflabel="Relation between directories">
+ <sect1 id="intro-usage-conbdirs">
<title>Relation Between Directories</title>
@@ -191,7 +200,7 @@
</sect1>
- <sect1 id="intro-usage-syncro" xreflabel="Syncronizing paths">
+ <sect1 id="intro-usage-syncro">
<title>Syncronizing Paths</title>
@@ -267,8 +276,7 @@
</sect1>
- <sect1 id="intro-usage-extending" xreflabel="Extending repository
- organization">
+ <sect1 id="intro-usage-extending">
<title>Extending Repository Organization</title>
@@ -309,27 +317,32 @@
class="directory">trunk/Scripts</filename> stores automation
scripts.</para>
- <para>To better illustrate this desition process, you can
- consider to examin the <filename
- class="directory">trunk/Identity/Images/Themes/TreeFlower/3</filename>
- directory structure as example. This directory can be read
- as: the theme development line of version <quote>3</quote> of
- <quote>TreeFlower</quote> artistic motif. Additional, we can
- say that <quote>TreeFlower</quote> artistic motif is part of
- themes, as themes are part of The CentOS Project corporate
- visual identity.</para>
+ <para>
+ To better illustrate this desition process, you can
+ consider to examin the <filename
+ class="directory">trunk/Identity/Images/Themes/TreeFlower/3</filename>
+ directory structure as example. This directory can be
+ read as: the theme development line of version
+ <quote>3</quote> of <quote>TreeFlower</quote> artistic
+ motif. Additional, we can say that
+ <quote>TreeFlower</quote> artistic motif is part of
+ themes, as themes are part of The CentOS Project corporate
+ visual identity.
+ </para>
- <para>The relationship between conceptual ideas can be
- stablished by reading each repository documentation entry
- individually, from <filename
- class="directory">trunk</filename> directory to a deeper
- directory in the path. For reading repository documentation
- entries we use the <code>help</code> functionality of
- <command>centos-art.sh</command> script.</para>
+ <para>
+ The relationship between conceptual ideas can be
+ stablished by reading each repository documentation entry
+ individually, from <filename
+ class="directory">trunk</filename> directory to a deeper
+ directory in the path. For reading repository
+ documentation entries we use the <code>help</code>
+ functionality of <command>centos-art.sh</command> script.
+ </para>
</sect1>
- <sect1 id="intro-usage-filenames" xreflabel="File names convenction">
+ <sect1 id="intro-usage-filenames">
<title>File Names</title>
@@ -354,9 +367,9 @@
</sect1>
- <sect1 id="intro-usage-layout" xreflabel="Repository layout">
+ <sect1 id="intro-usage-layout">
- <title>Repository Layout</title>
+ <title>Layout</title>
<para>The CentOS Artwork Repository is organized through a
convenctional <quote>trunk</quote>, <quote>branches</quote>
diff --git a/Manuals/Repository/Docbook/Manuals/Texinfo/structure.docbook b/Manuals/Repository/Docbook/Manuals/Texinfo/structure.docbook
index f79669a..544b088 100644
--- a/Manuals/Repository/Docbook/Manuals/Texinfo/structure.docbook
+++ b/Manuals/Repository/Docbook/Manuals/Texinfo/structure.docbook
@@ -62,7 +62,7 @@
<para>
Licenses — This chapter includes licenses from
<filename
- class="directory">trunk/Scripts/Functions/Help/Texinfo/Templates/$LANG/Licenses/</filename>
+ class="directory">trunk/Scripts/Functions/Help/Texinfo/Templates/<replaceable>language</replaceable>/Licenses/</filename>
directory. In the normal work flow, you don't need to
touch this chapter. It is created when the document
structure is created and should ramain that way. If you
@@ -105,7 +105,7 @@
<mediaobject>
<textobject>
<programlisting>trunk/Manuals/Repository/Texinfo
-|-- $LANG
+|-- en_US
| |-- Directories
| | |-- chapter-menu.texinfo
| | |-- chapter-nodes.texinfo