Update Shell.xml - title case

This commit is contained in:
Mirek Jahoda 2017-10-23 15:29:56 +00:00
parent db9a3e424e
commit 6882e1f2af

View file

@ -11,7 +11,7 @@
comparable syntax.
</para>
<section id="sect-Defensive_Coding-Shell-Alternatives">
<title>Consider alternatives</title>
<title>Consider Alternatives</title>
<para>
Once a shell script is so complex that advice in this chapter
applies, it is time to step back and consider the question: Is
@ -26,7 +26,7 @@
</para>
</section>
<section id="sect-Defensive_Coding-Shell-Language">
<title>Shell language features</title>
<title>Shell Language Features</title>
<para>
The following sections cover subtleties concerning the shell
programming languages. They have been written with the
@ -40,7 +40,7 @@
programming language.
</para>
<section id="sect-Defensive_Coding-Shell-Parameter_Expansion">
<title>Parameter expansion</title>
<title>Parameter Expansion</title>
<para>
The mechanism by which named shell variables and parameters are
expanded is called <emphasis>parameter expansion</emphasis>. The
@ -73,7 +73,7 @@ external-program "$arg1" "$arg2"
</para>
</section>
<section id="sect-Defensive_Coding-Shell-Double_Expansion">
<title>Double expansion</title>
<title>Double Expansion</title>
<para>
<emphasis>Double expansion</emphasis> occurs when, during the
expansion of a shell variable, not just the variable is expanded,
@ -103,7 +103,7 @@ external-program "$arg1" "$arg2"
double expansion occurs.
</para>
<section id="sect-Defensive_Coding-Shell-Arithmetic">
<title>Arithmetic evaluation</title>
<title>Arithmetic Evaluation</title>
<para>
<emphasis>Arithmetic evaluation</emphasis> is a process by which
the shell computes the integer value of an expression specified
@ -270,7 +270,7 @@ array_variable=(1 2 3 4)
</section>
</section>
<section id="sect-Defensive_Coding-Shell-Obscure">
<title>Other obscurities</title>
<title>Other Obscurities</title>
<para>
Obscure shell language features should not be used. Examples are:
</para>
@ -303,7 +303,7 @@ array_variable=(1 2 3 4)
</section>
</section>
<section id="sect-Defensive_Coding-Shell-Invoke">
<title>Invoking external commands</title>
<title>Invoking External Commands</title>
<para>
When passing shell variables as single command line arguments,
they should always be surrounded by double quotes. See
@ -361,7 +361,7 @@ array_variable=(1 2 3 4)
</para>
</section>
<section id="sect-Defensive_Coding-Shell-Temporary_Files">
<title>Temporary files</title>
<title>Temporary Files</title>
<para>
Temporary files should be created with the
<literal>mktemp</literal> command, and temporary directories with
@ -375,7 +375,7 @@ array_variable=(1 2 3 4)
variables.
</para>
<example id="ex-Defensive_Coding-Tasks-Temporary_Files">
<title>Creating and cleaning up temporary files</title>
<title>Creating and Cleaning up Temporary Files</title>
<informalexample>
<programlisting language="Bash">
tmpfile="$(mktemp)"
@ -390,7 +390,7 @@ trap cleanup 0
</example>
</section>
<section id="sect-Defensive_Coding-Shell-Input_Validation">
<title>Performing input validation</title>
<title>Performing Input Validation</title>
<para>
In some cases, input validation cannot be avoided. For example,
if arithmetic evaluation is absolutely required, it is imperative
@ -422,7 +422,7 @@ trap cleanup 0
</para>
</section>
<section id="sect-Defensive_Coding-Shell-Edit_Guard">
<title>Guarding shell scripts against changes</title>
<title>Guarding Shell Scripts Against Changes</title>
<para>
<application>bash</application> only reads a shell script up to
the point it is needed for executed the next command. This means