Many pages: Use a consistent style for lists

There are different kinds of lists:

Tagged paragraphs
	These are fixed in a separate commit (the previous one).
	They are used for a list of tags and their descriptions.
	An example is this commit message itself.

Ordered lists
	Elements are preceeded by a number in parentheses.
	These represent a set of steps that have an order.

	When there are substeps, they will be numbered like (4.2).

Positional lists
	Elements are preceeded by a number in square brackets
	(index).  These represent fields in a set.  The index will
	start at:

	0	fields of a C data structure, to be consistent
		with arrays.
	1	fields of a file, to be consistent with tools like
		cut(1).

Alternatives list
	Elements are preceeded by a letter in parentheses.
	These represent a set of (normally) exclusive
	alternatives.

Bullet lists
	Elements are preceeded by bullet symbols.  Anything that
	doesn't fit elsewhere usually is covered by this type of
	list.

Notes
	Not really a list, but the syntax is identical to
	"positional lists".

There should always be 2 spaces between the list symbol and the
elements.  This doesn't apply to "tagged paragraphs", which use
the default indentation rules.

Reported-by: Mike Frysinger <vapier@gentoo.org>
Cc: <groff@gnu.org>
Acked-by: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Signed-off-by: Alejandro Colomar <alx@kernel.org>

1 files changed, 13 insertions, 13 deletions

diff --git a/man8/ld.so.8 b/man8/ld.so.8
index bcdb2f0ab..5f790323d 100644
--- a/man8/ld.so.8
+++ b/man8/ld.so.8
@@ -57,17 +57,17 @@ and the shared object is loaded using that pathname.
 .PP
 If a shared object dependency does not contain a slash,
 then it is searched for in the following order:
-.IP o 3
+.IP (1) 5
 Using the directories specified in the
 DT_RPATH dynamic section attribute
 of the binary if present and DT_RUNPATH attribute does not exist.
 Use of DT_RPATH is deprecated.
-.IP o
+.IP (2)
 Using the environment variable
 .BR LD_LIBRARY_PATH ,
 unless the executable is being run in secure-execution mode (see below),
 in which case this variable is ignored.
-.IP o
+.IP (3)
 Using the directories specified in the
 DT_RUNPATH dynamic section attribute
 of the binary if present.
@@ -77,7 +77,7 @@ and do not apply to those objects' children,
 which must themselves have their own DT_RUNPATH entries.
 This is unlike DT_RPATH, which is applied
 to searches for all children in the dependency tree.
-.IP o
+.IP (4)
 From the cache file
 .IR /etc/ld.so.cache ,
 which contains a compiled list of candidate shared objects previously found
@@ -87,7 +87,7 @@ If, however, the binary was linked with the
 linker option, shared objects in the default paths are skipped.
 Shared objects installed in hardware capability directories (see below)
 are preferred to other shared objects.
-.IP o
+.IP (5)
 In the default path
 .IR /lib ,
 and then
@@ -102,13 +102,13 @@ linker option, this step is skipped.
 .\"
 .SS Dynamic string tokens
 In several places, the dynamic linker expands dynamic string tokens:
-.IP o 3
+.IP \(bu 3
 In the environment variables
 .BR LD_LIBRARY_PATH ,
 .BR LD_PRELOAD ,
 and
 .BR LD_AUDIT ,
-.IP o 3
+.IP \(bu
 inside the values of the dynamic section tags
 .BR DT_NEEDED ,
 .BR DT_RPATH ,
@@ -117,7 +117,7 @@ inside the values of the dynamic section tags
 and
 .B DT_DEPAUDIT
 of ELF binaries,
-.IP o 3
+.IP \(bu
 in the arguments to the
 .B ld.so
 command line options
@@ -126,7 +126,7 @@ command line options
 and
 .B \-\-preload
 (see below), and
-.IP o 3
+.IP \(bu
 in the filename arguments to the
 .BR dlopen (3)
 and
@@ -296,15 +296,15 @@ entry in the auxiliary vector (see
 .BR getauxval (3))
 has a nonzero value.
 This entry may have a nonzero value for various reasons, including:
-.IP * 3
+.IP \(bu 3
 The process's real and effective user IDs differ,
 or the real and effective group IDs differ.
 This typically occurs as a result of executing
 a set-user-ID or set-group-ID program.
-.IP *
+.IP \(bu
 A process with a non-root user ID executed a binary that
 conferred capabilities to the process.
-.IP *
+.IP \(bu
 A nonzero value may have been set by a Linux Security Module.
 .\"
 .SS Environment variables
@@ -438,7 +438,7 @@ as described above in
 There are various methods of specifying libraries to be preloaded,
 and these are handled in the following order:
 .RS
-.IP (1) 4
+.IP (1) 5
 The
 .B LD_PRELOAD
 environment variable.