From 9bfe1b3936927549bb985d0fed172af50d075ef0 Mon Sep 17 00:00:00 2001
From: Michael Kerrisk <mtk.manpages@gmail.com>
Date: Fri, 15 Jun 2007 19:53:05 +0000
Subject: [PATCH] Reformatted headings; minor rewrites.

---
 man7/sem_overview.7 | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/man7/sem_overview.7 b/man7/sem_overview.7
index 752d2b238..fc7d180f9 100644
--- a/man7/sem_overview.7
+++ b/man7/sem_overview.7
@@ -38,7 +38,8 @@ operation will block until the value becomes greater than zero.
 
 POSIX semaphores come in two forms: named semaphores and
 unnamed semaphores.
-.SS Named semaphores
+.TP
+.B Named semaphores
 A named semaphore is identified by a name of the form
 .IR /somename .
 Two processes can operate on the same named semaphore by passing
@@ -59,7 +60,8 @@ to close the semaphore.
 When all processes have finished using the semaphore,
 it can be removed from the system using
 .BR sem_unlink (3).
-.SS Unnamed semaphores (memory-based semaphores)
+.TP
+.B Unnamed semaphores (memory-based semaphores)
 An unnamed semaphore does not have a name.
 Instead the semaphore is placed in a region of memory that
 is shared between multiple threads (a
@@ -84,7 +86,9 @@ When the semaphore is no longer required,
 and before the memory in which it is located is deallocated,
 the semaphore should be destroyed using
 .BR sem_destroy (3).
-.SH LINUX SPECIFIC DETAILS
+.PP
+The remainder of this section describes some specific details
+of the Linux implementation of POSIX semaphores.
 .SS Versions
 Prior to kernel 2.6, Linux only supported unnamed,
 thread-shared semaphores.