1 |
>>>>> On Wed, 12 Apr 2017, Ulrich Mueller wrote: |
2 |
|
3 |
> Fine with me. We start with \chapter though, so \subsection is at |
4 |
> level 3 already (and should be the first level with sentence case |
5 |
> if we follow APA). |
6 |
|
7 |
Patch is below. |
8 |
|
9 |
Ulrich |
10 |
|
11 |
|
12 |
From ce8990bdcf56da5a9360cc273e4f8661af5497a6 Mon Sep 17 00:00:00 2001 |
13 |
From: =?UTF-8?q?Ulrich=20M=C3=BCller?= <ulm@g.o> |
14 |
Date: Fri, 14 Apr 2017 10:21:27 +0200 |
15 |
Subject: [PATCH] More consistent capitalisation of headings. |
16 |
|
17 |
Use title case for first and second level headings (i.e., \chapter |
18 |
and \section in the main text, \section and \subsection in the EAPI |
19 |
cheat sheet); use sentence case everywhere else. |
20 |
|
21 |
https://archives.gentoo.org/gentoo-pms/message/cef75e03f1a3b692281a5b79065dc2b6 |
22 |
--- |
23 |
appendices.tex | 2 +- |
24 |
dependencies.tex | 20 ++++++++++---------- |
25 |
ebuild-env-commands.tex | 4 ++-- |
26 |
ebuild-env-invariancy.tex | 2 +- |
27 |
ebuild-env-state.tex | 2 +- |
28 |
ebuild-env-vars.tex | 6 +++--- |
29 |
ebuild-functions.tex | 4 ++-- |
30 |
ebuild-vars.tex | 4 ++-- |
31 |
eclasses.tex | 2 +- |
32 |
merge.tex | 6 +++--- |
33 |
names.tex | 18 +++++++++--------- |
34 |
pkg-mgr-commands.tex | 10 +++++----- |
35 |
profile-variables.tex | 4 ++-- |
36 |
profiles.tex | 4 ++-- |
37 |
14 files changed, 44 insertions(+), 44 deletions(-) |
38 |
|
39 |
diff --git a/appendices.tex b/appendices.tex |
40 |
index 99429ec..1b70568 100644 |
41 |
--- a/appendices.tex |
42 |
+++ b/appendices.tex |
43 |
@@ -30,7 +30,7 @@ The items described in this chapter are included for information only. Unless ot |
44 |
they were deprecated or abandoned long before \t{EAPI} was introduced. Ebuilds must not use these |
45 |
features, and package managers should not be changed to support them. |
46 |
|
47 |
-\section{If-else use blocks} |
48 |
+\section{If-else USE Blocks} |
49 |
|
50 |
Historically, Portage supported if-else use conditionals, as shown by |
51 |
listing~\ref{lst:if-else-use-listing}. The block before the colon would be taken if the condition |
52 |
diff --git a/dependencies.tex b/dependencies.tex |
53 |
index 9917bc4..ee4339b 100644 |
54 |
--- a/dependencies.tex |
55 |
+++ b/dependencies.tex |
56 |
@@ -117,11 +117,11 @@ In particular, note that whitespace is not optional. |
57 |
\end{tabular} |
58 |
\end{centertable} |
59 |
|
60 |
-\subsection{All-of Dependency Specifications} |
61 |
+\subsection{All-of dependency specifications} |
62 |
|
63 |
In an all-of group, all of the child elements must be matched. |
64 |
|
65 |
-\subsection{Use-conditional Dependency Specifications} |
66 |
+\subsection{USE-conditional dependency specifications} |
67 |
|
68 |
In a use-conditional group, if the associated use flag is enabled (or disabled if it has an |
69 |
exclamation mark prefix), all of the child elements must be matched. |
70 |
@@ -129,7 +129,7 @@ exclamation mark prefix), all of the child elements must be matched. |
71 |
It is an error for a flag to be used if it is not included in \t{IUSE\_EFFECTIVE} as described in |
72 |
section~\ref{sec:use-iuse-handling}. |
73 |
|
74 |
-\subsection{Any-of Dependency Specifications} |
75 |
+\subsection{Any-of dependency specifications} |
76 |
|
77 |
Any use-conditional group that is an immediate child of an any-of group, if not enabled (disabled |
78 |
for an exclamation mark prefixed use flag name), is not considered a member of the any-of group |
79 |
@@ -140,7 +140,7 @@ considered to be matched if its associated package dependency specification is n |
80 |
|
81 |
An empty any-of group counts as being matched. |
82 |
|
83 |
-\subsection{Exactly-one-of Dependency Specifications} |
84 |
+\subsection{Exactly-one-of dependency specifications} |
85 |
|
86 |
Any use-conditional group that is an immediate child of an exactly-one-of group, if not enabled |
87 |
(disabled for an exclamation mark prefixed use flag name), is not considered a member of the |
88 |
@@ -150,7 +150,7 @@ In an exactly-one-of group, exactly one immediate child element must be matched. |
89 |
|
90 |
An empty exactly-one-of group counts as being matched. |
91 |
|
92 |
-\subsection{At-most-one-of Dependency Specifications} |
93 |
+\subsection{At-most-one-of dependency specifications} |
94 |
|
95 |
Any use-conditional group that is an immediate child of an at-most-one-of group, if not enabled |
96 |
(disabled for an exclamation mark prefixed use flag name), is not considered a member of the |
97 |
@@ -160,7 +160,7 @@ In an at-most-one-of group, at most one immediate child element must be matched. |
98 |
|
99 |
An empty at-most-one-of group counts as being matched. |
100 |
|
101 |
-\subsection{Package Dependency Specifications} |
102 |
+\subsection{Package dependency specifications} |
103 |
|
104 |
A package dependency can be in one of the following base formats. A package manager must warn or |
105 |
error on non-compliant input. |
106 |
@@ -232,7 +232,7 @@ The following operators are available: |
107 |
\item[\t{>}] Strictly greater than the specified version. |
108 |
\end{description} |
109 |
|
110 |
-\subsubsection{Block Operator} |
111 |
+\subsubsection{Block operator} |
112 |
|
113 |
If the specification is prefixed with one or two exclamation marks, the named dependency is a block |
114 |
rather than a requirement---that is to say, the specified package must not be installed, with the |
115 |
@@ -263,7 +263,7 @@ described in table~\ref{tab:bang-strength-table}. |
116 |
\end{tabular} |
117 |
\end{centertable} |
118 |
|
119 |
-\subsubsection{Slot Dependencies} |
120 |
+\subsubsection{Slot dependencies} |
121 |
\label{sec:slot-dep} |
122 |
|
123 |
\featurelabel{slot-deps} A named slot dependency consists of a colon followed by a slot name. A |
124 |
@@ -300,7 +300,7 @@ Whenever the equals slot operator is used in an enabled dependency group, the de |
125 |
(\t{DEPEND}) must ensure that a matching package is installed at build time. It is invalid to use |
126 |
the equals slot operator inside \t{PDEPEND} or inside any-of dependency specifications. |
127 |
|
128 |
-\subsubsection{2-Style and 4-Style Use Dependencies} |
129 |
+\subsubsection{2-style and 4-style USE dependencies} |
130 |
\label{sec:use-dep} |
131 |
|
132 |
A 2-style or 4-style use dependency consists of one of the following: |
133 |
@@ -338,7 +338,7 @@ would not have to be part of \t{IUSE}. |
134 |
It is an error for an ebuild to use a conditional use dependency when that ebuild does not have the |
135 |
flag in \t{IUSE\_EFFECTIVE}. |
136 |
|
137 |
-\subsection{Use State Constraints} |
138 |
+\subsection{USE state constraints} |
139 |
\label{sec:required-use} |
140 |
\t{REQUIRED\_USE} contains a list of assertions that must be met by the configuration of \t{USE} |
141 |
flags to be valid for this ebuild. In order to be matched, a \t{USE} flag in a terminal element |
142 |
diff --git a/ebuild-env-commands.tex b/ebuild-env-commands.tex |
143 |
index 5deb388..30c297c 100644 |
144 |
--- a/ebuild-env-commands.tex |
145 |
+++ b/ebuild-env-commands.tex |
146 |
@@ -1,4 +1,4 @@ |
147 |
-\section{Available commands} |
148 |
+\section{Available Commands} |
149 |
|
150 |
This section documents the commands available to an ebuild. Unless otherwise specified, they may be |
151 |
aliases, shell functions, or executables in the ebuild's \t{PATH}. |
152 |
@@ -60,7 +60,7 @@ In some cases a package's build process will require the availability of executa |
153 |
the core system, a common example being autotools. The availability of commands provided by the |
154 |
particular types of dependencies is explained in section~\ref{sec:dependency-classes}. |
155 |
|
156 |
-\subsection{Ebuild-specific Commands} |
157 |
+\subsection{Ebuild-specific commands} |
158 |
\input{pkg-mgr-commands.tex} |
159 |
|
160 |
% vim: set filetype=tex fileencoding=utf8 et tw=100 spell spelllang=en : |
161 |
diff --git a/ebuild-env-invariancy.tex b/ebuild-env-invariancy.tex |
162 |
index d69c510..861e6b9 100644 |
163 |
--- a/ebuild-env-invariancy.tex |
164 |
+++ b/ebuild-env-invariancy.tex |
165 |
@@ -1,4 +1,4 @@ |
166 |
-\section{The state of the system between functions} |
167 |
+\section{The State of the System Between Functions} |
168 |
|
169 |
For the sake of this section: |
170 |
|
171 |
diff --git a/ebuild-env-state.tex b/ebuild-env-state.tex |
172 |
index 3ddd1ab..70a0e46 100644 |
173 |
--- a/ebuild-env-state.tex |
174 |
+++ b/ebuild-env-state.tex |
175 |
@@ -1,4 +1,4 @@ |
176 |
-\section{The state of variables between functions} |
177 |
+\section{The State of Variables Between Functions} |
178 |
\label{sec:ebuild-env-state} |
179 |
|
180 |
Exported and default scope variables are saved between functions. A non-local variable set in a |
181 |
diff --git a/ebuild-env-vars.tex b/ebuild-env-vars.tex |
182 |
index 019ce3f..ae47aea 100644 |
183 |
--- a/ebuild-env-vars.tex |
184 |
+++ b/ebuild-env-vars.tex |
185 |
@@ -312,7 +312,7 @@ table~\ref{tab:locale-settings}. |
186 |
\end{tabular} |
187 |
\end{centertable} |
188 |
|
189 |
-\subsection{USE and IUSE Handling} |
190 |
+\subsection{USE and IUSE handling} |
191 |
\label{sec:use-iuse-handling} |
192 |
|
193 |
This section discusses the handling of four variables: |
194 |
@@ -377,7 +377,7 @@ For EAPIs listed in table~\ref{tab:profile-iuse-injection-table} as supporting p |
195 |
\t{IUSE} injection, the package manager must save the calculated value of \t{IUSE\_EFFECTIVE} when |
196 |
installing a package. Details are beyond the scope of this specification. |
197 |
|
198 |
-\subsection{\t{REPLACING\_VERSIONS} and \t{REPLACED\_BY\_VERSION}} |
199 |
+\subsection{REPLACING\_VERSIONS and REPLACED\_BY\_VERSION} |
200 |
\label{sec:replacing-versions} |
201 |
|
202 |
\featurelabel{replace-version-vars} In EAPIs listed in table~\ref{tab:added-env-vars-table} as |
203 |
@@ -393,7 +393,7 @@ In EAPIs listed in table~\ref{tab:added-env-vars-table} as supporting it, the |
204 |
\t{REPLACED\_BY\_VERSION} variable shall be defined in \t{pkg\_prerm} and \t{pkg\_postrm}. It shall |
205 |
contain at most one value. |
206 |
|
207 |
-\subsection{Offset-prefix variables \t{EPREFIX}, \t{EROOT} and \t{ED}} |
208 |
+\subsection{Offset-prefix variables} |
209 |
\label{sec:offset-vars} |
210 |
|
211 |
\ChangeWhenAddingAnEAPI{6} |
212 |
diff --git a/ebuild-functions.tex b/ebuild-functions.tex |
213 |
index a744ae1..045b207 100644 |
214 |
--- a/ebuild-functions.tex |
215 |
+++ b/ebuild-functions.tex |
216 |
@@ -18,7 +18,7 @@ package, not the current configuration. |
217 |
|
218 |
Ebuilds must not call nor assume the existence of any phase functions. |
219 |
|
220 |
-\subsection{Initial Working Directories} |
221 |
+\subsection{Initial working directories} |
222 |
\label{sec:s-to-workdir-fallback} |
223 |
|
224 |
Some functions may assume that their initial working directory is set to a particular location; |
225 |
@@ -447,7 +447,7 @@ source files from their respective locations, with notes concerning licensing if |
226 |
|
227 |
\t{pkg\_nofetch} must require no write access to any part of the filesystem. |
228 |
|
229 |
-\subsection{\t{default\_} Phase Functions} |
230 |
+\subsection{Default phase functions} |
231 |
\label{sec:default-phase-funcs} |
232 |
|
233 |
\featurelabel{default-phase-funcs} In EAPIs listed in |
234 |
diff --git a/ebuild-vars.tex b/ebuild-vars.tex |
235 |
index ecb50df..9a9502e 100644 |
236 |
--- a/ebuild-vars.tex |
237 |
+++ b/ebuild-vars.tex |
238 |
@@ -8,7 +8,7 @@ If any of these variables are set to invalid values, or if any of the mandatory |
239 |
undefined, the package manager's behaviour is undefined; ideally, an error in one ebuild should not |
240 |
prevent operations upon other ebuilds or packages. |
241 |
|
242 |
-\section{Metadata invariance} |
243 |
+\section{Metadata Invariance} |
244 |
\label{sec:metadata-invariance} |
245 |
|
246 |
All ebuild-defined variables discussed in this chapter must be defined independently of |
247 |
@@ -163,7 +163,7 @@ unlisted architectures. |
248 |
|
249 |
An empty \t{KEYWORDS} variable indicates uncertain functionality on any architecture. |
250 |
|
251 |
-\subsection{\t{RDEPEND} value} |
252 |
+\subsection{RDEPEND value} |
253 |
\label{sec:rdepend-depend} |
254 |
|
255 |
\featurelabel{rdepend-depend} In EAPIs listed in table~\ref{tab:rdepend-depend-table} as having |
256 |
diff --git a/eclasses.tex b/eclasses.tex |
257 |
index 51c9a83..7569caf 100644 |
258 |
--- a/eclasses.tex |
259 |
+++ b/eclasses.tex |
260 |
@@ -11,7 +11,7 @@ Eclasses must be located in the \t{eclass} directory in the top level of the rep |
261 |
section~\ref{sec:eclass-dir}. Each eclass is a single file named \t{<name>.eclass}, where \t{<name>} is |
262 |
the name of this eclass, used by \t{inherit} and \t{EXPORT\_FUNCTIONS} among other places. |
263 |
|
264 |
-\section{The inherit command} |
265 |
+\section{The inherit Command} |
266 |
\label{sec:inherit} |
267 |
|
268 |
An ebuild wishing to make use of an eclass does so by using the \t{inherit} command in global scope. |
269 |
diff --git a/merge.tex b/merge.tex |
270 |
index 9da9631..0077837 100644 |
271 |
--- a/merge.tex |
272 |
+++ b/merge.tex |
273 |
@@ -33,7 +33,7 @@ except as follows: |
274 |
On SELinux systems, the SELinux context must also be preserved. Other directory attributes, including |
275 |
modification time, may be discarded. |
276 |
|
277 |
-\subsection{Empty Directories} |
278 |
+\subsection{Empty directories} |
279 |
|
280 |
Behaviour upon encountering an empty directory is undefined. Ebuilds must not attempt to install an |
281 |
empty directory. |
282 |
@@ -100,7 +100,7 @@ is undefined. |
283 |
\end{tabular} |
284 |
\end{centertable} |
285 |
|
286 |
-\subsection{Configuration File Protection} |
287 |
+\subsection{Configuration file protection} |
288 |
\label{sec:config-protect} |
289 |
|
290 |
The package manager must provide a means to prevent user configuration files from being |
291 |
@@ -141,7 +141,7 @@ Ebuilds must not attempt to merge a symlink on top of a directory. |
292 |
Any absolute symlink whose link starts with \t{D} must be rewritten with the leading \t{D} removed. |
293 |
The package manager should issue a notice when doing this. |
294 |
|
295 |
-\section{Hard links} |
296 |
+\section{Hard Links} |
297 |
|
298 |
A hard link may be merged either as a single file with links or as multiple independent files. |
299 |
|
300 |
diff --git a/names.tex b/names.tex |
301 |
index e4c3975..a348c0f 100644 |
302 |
--- a/names.tex |
303 |
+++ b/names.tex |
304 |
@@ -5,14 +5,14 @@ |
305 |
No name may be empty. Package managers must not impose fixed upper boundaries upon the length of any |
306 |
name. A package manager should indicate or reject any name that is invalid according to these rules. |
307 |
|
308 |
-\subsection{Category Names} |
309 |
+\subsection{Category names} |
310 |
A category name may contain any of the characters [\t{A-Za-z0-9+\_.-}]. It must not begin with |
311 |
a hyphen, a dot or a plus sign. |
312 |
|
313 |
\note A hyphen is \e{not} required because of the \t{virtual} category. Usually, however, category |
314 |
names will contain a hyphen. |
315 |
|
316 |
-\subsection{Package Names} |
317 |
+\subsection{Package names} |
318 |
A package name may contain any of the characters [\t{A-Za-z0-9+\_-}]. It must not begin with a |
319 |
hyphen or a plus sign, and must not end in a hyphen followed by anything matching the version |
320 |
syntax described in section~\ref{sec:version-spec}. |
321 |
@@ -20,35 +20,35 @@ syntax described in section~\ref{sec:version-spec}. |
322 |
\note A package name does not include the category. The term \i{qualified package name} is used |
323 |
where a \t{category/package} pair is meant. |
324 |
|
325 |
-\subsection{Slot Names} |
326 |
+\subsection{Slot names} |
327 |
\label{sec:slot-names} |
328 |
A slot name may contain any of the characters [\t{A-Za-z0-9+\_.-}]. It must not begin with a |
329 |
hyphen, a dot or a plus sign. |
330 |
|
331 |
-\subsection{USE Flag Names} |
332 |
+\subsection{USE flag names} |
333 |
A USE flag name may contain any of the characters [\t{A-Za-z0-9+\_@-}]. It must begin with an |
334 |
alphanumeric character. Underscores should be considered reserved for \t{USE\_EXPAND}, as |
335 |
described in section~\ref{sec:use-iuse-handling}. |
336 |
|
337 |
\note The at-sign is required for \t{LINGUAS}. |
338 |
|
339 |
-\subsection{Repository Names} |
340 |
+\subsection{Repository names} |
341 |
\label{sec:repository-names} |
342 |
A repository name may contain any of the characters [\t{A-Za-z0-9\_-}]. It must not begin with a |
343 |
hyphen. In addition, every repository name must also be a valid package name. |
344 |
|
345 |
-\subsection{License Names} |
346 |
+\subsection{License names} |
347 |
\label{sec:license-names} |
348 |
A license name may contain any of the characters [\t{A-Za-z0-9+\_.-}]. It must not begin with a |
349 |
hyphen, a dot or a plus sign. |
350 |
|
351 |
-\subsection{Keyword Names} |
352 |
+\subsection{Keyword names} |
353 |
\label{sec:keyword-names} |
354 |
A keyword name may contain any of the characters [\t{A-Za-z0-9\_-}]. It must not begin with a |
355 |
hyphen. In contexts where it makes sense to do so, a keyword name may be prefixed by |
356 |
a tilde or a hyphen. In \t{KEYWORDS}, \t{-*} is also acceptable as a keyword. |
357 |
|
358 |
-\subsection{EAPI Names} |
359 |
+\subsection{EAPI names} |
360 |
\label{sec:eapi-names} |
361 |
An EAPI name may contain any of the characters [\t{A-Za-z0-9+\_.-}]. It must not begin with a |
362 |
hyphen, a dot or a plus sign. |
363 |
@@ -207,7 +207,7 @@ from which it was invoked. |
364 |
\end{algorithmic} |
365 |
\end{algorithm} |
366 |
|
367 |
-\section{Uniqueness of versions} |
368 |
+\section{Uniqueness of Versions} |
369 |
|
370 |
No two packages in a given repository may have the same qualified package name and equal versions. |
371 |
For example, a repository may not contain more than one of \t{foo-bar/baz-1.0.2}, |
372 |
diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex |
373 |
index 389d8c0..7da9d4b 100644 |
374 |
--- a/pkg-mgr-commands.tex |
375 |
+++ b/pkg-mgr-commands.tex |
376 |
@@ -718,7 +718,7 @@ in table~\ref{tab:compression-table} as supporting \t{docompress}. |
377 |
\end{tabular} |
378 |
\end{centertable} |
379 |
|
380 |
-\subsubsection{Use List Functions} |
381 |
+\subsubsection{USE list functions} |
382 |
These functions provide behaviour based upon set or unset use flags. Ebuilds must not run any of |
383 |
these commands once the current phase function has returned. It is an error if an ebuild calls any |
384 |
of these functions in global scope. |
385 |
@@ -800,7 +800,7 @@ table~\ref{tab:use-list-strictness}. |
386 |
\end{tabular} |
387 |
\end{centertable} |
388 |
|
389 |
-\subsubsection{Text List Functions} |
390 |
+\subsubsection{Text list functions} |
391 |
These functions check whitespace-separated lists for a particular value. |
392 |
|
393 |
\begin{description} |
394 |
@@ -810,7 +810,7 @@ These functions check whitespace-separated lists for a particular value. |
395 |
\item[hasq] Deprecated synonym for \t{has}. |
396 |
\end{description} |
397 |
|
398 |
-\subsubsection{Misc Commands} |
399 |
+\subsubsection{Misc commands} |
400 |
The following commands are always available in the ebuild environment, but don't really fit in any |
401 |
of the above categories. Ebuilds must not run any of these commands once the current phase function |
402 |
has returned. |
403 |
@@ -987,7 +987,7 @@ has returned. |
404 |
\end{tabular} |
405 |
\end{centertable} |
406 |
|
407 |
-\subsubsection{Debug Commands} |
408 |
+\subsubsection{Debug commands} |
409 |
The following commands are available for debugging. Normally all of these commands should be no ops; |
410 |
a package manager may provide a special debug mode where these commands instead do something. |
411 |
Ebuilds must not run any of these commands once the current phase function has returned. |
412 |
@@ -1000,7 +1000,7 @@ Ebuilds must not run any of these commands once the current phase function has r |
413 |
\item[debug-print-section] Calls \t{debug-print} with \t{now in section \$*}. |
414 |
\end{description} |
415 |
|
416 |
-\subsubsection{Reserved Commands and Variables} |
417 |
+\subsubsection{Reserved commands and variables} |
418 |
|
419 |
Except where documented otherwise, all functions and variables that contain any of the following |
420 |
strings (ignoring case) are reserved for package manager use and may not be used or relied upon by |
421 |
diff --git a/profile-variables.tex b/profile-variables.tex |
422 |
index c47b748..5fd2d8b 100644 |
423 |
--- a/profile-variables.tex |
424 |
+++ b/profile-variables.tex |
425 |
@@ -1,10 +1,10 @@ |
426 |
-\section{Profile variables} |
427 |
+\section{Profile Variables} |
428 |
\label{sec:profile-variables} |
429 |
|
430 |
This section documents variables that have special meaning, or special behaviour, when defined in a |
431 |
profile's \t{make.defaults} file. |
432 |
|
433 |
-\subsection{Incremental Variables} |
434 |
+\subsection{Incremental variables} |
435 |
\i{Incremental} variables must stack between parent and child profiles in the following manner: |
436 |
Beginning with the highest parent profile, tokenise the variable's value based on whitespace and |
437 |
concatenate the lists. Then, for any token $T$ beginning with a hyphen, remove it and any previous |
438 |
diff --git a/profiles.tex b/profiles.tex |
439 |
index ff791ac..2d0656d 100644 |
440 |
--- a/profiles.tex |
441 |
+++ b/profiles.tex |
442 |
@@ -1,7 +1,7 @@ |
443 |
\chapter{Profiles} |
444 |
\label{sec:profiles} |
445 |
|
446 |
-\section{General principles} |
447 |
+\section{General Principles} |
448 |
Generally, a profile defines information specific to a certain `type' of system---it lies somewhere |
449 |
between repository-level defaults and user configuration in that the information it contains is not |
450 |
necessarily applicable to all machines, but is sufficiently general that it should not be left to |
451 |
@@ -13,7 +13,7 @@ the files described in this chapter, and possibly inheriting another profile. Th |
452 |
follow a few basic conventions as regards inheritance and format; these are described in the next |
453 |
section. It may also contain any number of subdirectories containing other profiles. |
454 |
|
455 |
-\section{Files that make up a profile} |
456 |
+\section{Files That Make up a Profile} |
457 |
|
458 |
\subsection{The parent file} |
459 |
A profile may contain a \t{parent} file. Each line must contain a relative path to another profile |
460 |
-- |
461 |
2.12.2 |