# HG changeset patch
# User meillo@marmaro.de
# Date 1266785753 -3600
# Node ID f89ca78f289e60b5731d034651cdab334473d780
# Parent  00e306ee903b040ec8af1dae42dc526672227ff3
numbered 2nd level headings

diff -r 00e306ee903b -r f89ca78f289e unix-phil.ms
--- a/unix-phil.ms	Sun Feb 21 17:33:23 2010 +0100
+++ b/unix-phil.ms	Sun Feb 21 21:55:53 2010 +0100
@@ -219,7 +219,7 @@
 This chapter explains the philosophy, oriented on Gancarz,
 and shows concrete examples of its application.
 
-.SH
+.NH 2
 Pipes
 .LP
 Following are some examples to demonstrate how applied Unix Philosophy feels like.
@@ -292,7 +292,7 @@
 The other is the design of the programs that are used in the pipeline.
 They have to interfaces that allows them to be used in such a way.
 
-.SH
+.NH 2
 Interface design
 .LP
 Unix is, first of all, simple \(en Everything is a file.
@@ -345,7 +345,7 @@
 Testing of interactive programs is much more complicated,
 than testing of non-interactive programs.
 
-.SH
+.NH 2
 The toolchest approach
 .LP
 A toolchest is a set of tools.
@@ -423,7 +423,7 @@
 This script acts like the one before, when called without an argument.
 But one can also specify a numerical argument to define the number of lines to print.
 
-.SH
+.NH 2
 A powerful shell
 .LP
 It was already said, that the Unix shell provides the possibility to
@@ -487,7 +487,7 @@
 changing requirements.
 Software parts that are not written will not miss the requirements.
 
-.SH
+.NH 2
 Worse is better
 .LP
 The Unix Philosophy aims for the 80% solution;
@@ -527,7 +527,7 @@
 then less effort was spent into the project, than it would have be
 when a different approach had been used.
 
-.SH
+.NH 2
 Upgrowth and survival of software
 .LP
 So far it was talked about \fIwriting\fP or \fIbuilding\fP software.
@@ -634,7 +634,7 @@
 Who cares if the large program is a failure,
 but parts of it become successful instead?
 
-.SH
+.NH 2
 Summary
 .LP
 This chapter explained the central ideas of the Unix Philosophy.