From d9d9d7825ccf519b79878277669d4d311a686bb6 Mon Sep 17 00:00:00 2001
From: Miroslav Grepl <mgrepl@redhat.com>
Date: Mon, 29 Sep 2014 09:45:21 +0200
Subject: [PATCH 1/5] Fix semanage man page to talk about  semanage-* (8) man
 pages.

---
 policycoreutils/semanage/semanage.8 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/policycoreutils/semanage/semanage.8 b/policycoreutils/semanage/semanage.8
index fd27cf2..5d09d92 100644
--- a/policycoreutils/semanage/semanage.8
+++ b/policycoreutils/semanage/semanage.8
@@ -51,9 +51,9 @@ to SELinux user identities (which controls the initial security context
 assigned to Linux users when they login and bounds their authorized role set)
 as well as security context mappings for various kinds of objects, such
 as network ports, interfaces, and nodes (hosts) as well as the file
-context mapping. See the EXAMPLES section below for some examples
-of common usage.  Note that the semanage login command deals with the
-mapping from Linux usernames (logins) to SELinux user identities,
+context mapping. See the EXAMPLES section of semanage-* (8) man pages 
+for some examples of common usage.  Note that the semanage login command 
+deals with the mapping from Linux usernames (logins) to SELinux user identities,
 while the semanage user command deals with the mapping from SELinux
 user identities to authorized role sets.  In most cases, only the
 former mapping needs to be adjusted by the administrator; the latter
-- 
2.1.0