From 993f792f2e26f8a14a5e3691c06a6b15d57072e7 Mon Sep 17 00:00:00 2001 From: Sam Morris Date: Tue, 17 Sep 2024 12:43:08 +0100 Subject: [PATCH] Fix a couple of instances of the "no-break control character" being used inadvertently Fixes https://pagure.io/freeipa/issue/9665 Signed-off-by: Sam Morris Reviewed-By: Alexander Bokovoy --- client/man/ipa-client-install.1 | 4 ++-- client/man/ipa.1 | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/client/man/ipa-client-install.1 b/client/man/ipa-client-install.1 index 4a755ac33d35246304303b847a62cb3fc97680b7..725b114224781e2f7ec7c71eaf5b7be807008655 100644 --- a/client/man/ipa-client-install.1 +++ b/client/man/ipa-client-install.1 @@ -240,8 +240,8 @@ for more information. The option is mutually exclusive with \fB\-\-pkinit\-anchor\fR=\fIFILEDIR\fR Trust anchors (root and intermediate CA certs) for PKINIT. \fIFILEDIR\fR is either the absolute path to a PEM bundle (for example -'FILE:/etc/pki/tls/cert.pem') or to an OpenSSL hash directory (for example -'DIR:/etc/ssl/certs/'). The option can be used multiple times. PKINIT +\fIFILE:/etc/pki/tls/cert.pem\fR) or to an OpenSSL hash directory (for example +\fIDIR:/etc/ssl/certs/\fR). The option can be used multiple times. PKINIT requires the full trust chain of the Kerberos KDC server as well as the full trust chain of the identity certificate. diff --git a/client/man/ipa.1 b/client/man/ipa.1 index 172c50d8a1f2ba137ea10d93343fb54efbdb765d..c404c5be36da78ebb4d08cd0e4b2b9ea27d9e71b 100644 --- a/client/man/ipa.1 +++ b/client/man/ipa.1 @@ -176,11 +176,11 @@ journal as journald records execution context. See systemd.journal\-fields(7) for details. The details of the individual logged messages can be explained with the help of -'\fBjournalctl -x\fR' command, while full set of logged properties can be -retrieved with '\fBjournalctl -o json-pretty\fR'. See journalctl(1) for details +\fBjournalctl -x\fR command, while full set of logged properties can be +retrieved with \fBjournalctl -o json-pretty\fR. See journalctl(1) for details on the systemd journal viewer. -For the sample message above, an explanation could be requested with '\fBjournalctl -x -g ldap2_140328582446688\fR' where LDAP backend connection instance identifier can be used to uniquely fetch that individual message. +For the sample message above, an explanation could be requested with \fBjournalctl -x -g ldap2_140328582446688\fR where LDAP backend connection instance identifier can be used to uniquely fetch that individual message. .SH "EXAMPLES" .TP -- 2.47.0