From 12393d84a8e637a4bb1f3487bfb5f9702a4343ea Mon Sep 17 00:00:00 2001 From: Petr Bokoc Date: May 28 2020 14:58:37 +0000 Subject: Fix broken markup in Systemd.adoc --- diff --git a/guidelines/modules/ROOT/pages/Systemd.adoc b/guidelines/modules/ROOT/pages/Systemd.adoc index 1d90c2f..a13e97d 100644 --- a/guidelines/modules/ROOT/pages/Systemd.adoc +++ b/guidelines/modules/ROOT/pages/Systemd.adoc @@ -50,7 +50,7 @@ The `+Description=+` line must not exceed 80 characters, and must describe the s ====== Documentation field -Systemd in Fedora 17+ has support for defining documentation in unit files via the Documentation= field (it is ignored in older releases, so it is safe to keep one systemd unit file across all branches). System administrators will be looking at the contents of the Documentation= field to determine what the service is, how to configure it, and where to locate additional documentation relating to the service. Accordingly, packagers are strongly encouraged to include any available sources in the Documentation= field which provide this information. If a man page or info page is present in the package, refer to it using "man:manpage" or "info:infofile" respectively. If the documentation is in plaintext, use "file://path/to/file". Lastly, if no local documentation exists in the package, but it exists at a URL, use the URL (with http://) in this field. Multiple URIs can be added to the Documentation= field, as a space separated list. For details on URI definitions and formatting, please refer to the uri(7) manpage (man uri). +Systemd in Fedora 17+ has support for defining documentation in unit files via the `Documentation=` field (it is ignored in older releases, so it is safe to keep one systemd unit file across all branches). System administrators will be looking at the contents of the `Documentation=` field to determine what the service is, how to configure it, and where to locate additional documentation relating to the service. Accordingly, packagers are strongly encouraged to include any available sources in the `Documentation=` field which provide this information. If a man page or info page is present in the package, refer to it using `man:manpage` or `info:infofile` respectively. If the documentation is in plaintext, use `\file://path/to/file`. Lastly, if no local documentation exists in the package, but it exists at a URL, use the URL (with `http://`) in this field. Multiple URIs can be added to the `Documentation=` field, as a space separated list. For details on URI definitions and formatting, please refer to the `uri(7)` manpage (`man uri`). ===== [Service]