format subsection headers

modules/ROOT/pages/_partials/proc_converting-sysvinit-services.adoc

@@ -3,13 +3,13 @@
 
 Older versions of Fedora use SysVinit scripts to manage services. This section provides some guidelines on how to convert a SysVinit script to a systemd equivalent.
 
-.Prerequisites
+== Prerequisites
 
 * You are logged in as a user with administrator-level permissions.
 
 * You have a custom SysVinit script to convert to a systemd configuration.
 
-.Procedure
+== Procedure
 
 . Identify the runlevels in your SysVinit script. This is usually defined with `chkconfig` directive in the commented section at the beginning of the script. For example, the following indicates the service is using runlevels 3, 4, and 5:
 +
@@ -91,6 +91,6 @@ Alternatively, you can omit `ExecStop` and use the default behavior, which kills
 
 . Review the SysVinit script and identify any additional parameters or functions. Use systemd parameters to replicate any identified SysVinit functions that might be relevant to your service.
 
-.Related Information
+== Related Information
 
 * See link:#common-service-parameters[Common service parameters] for more information about the parameters used in this procedure.

modules/ROOT/pages/_partials/proc_creating-new-systemd-services.adoc

@@ -3,11 +3,11 @@
 
 This example shows how to create a unit file for a custom service. Custom unit files are located in `/etc/systemd/system/` and have a `.service` extension. For example, a custom `foo` service uses `/etc/systemd/system/foo.service` unit file.
 
-.Prerequisites
+== Prerequisites
 
 * You are logged in as a user with administrator-level permissions.
 
-.Procedure
+== Procedure
 
 This procedure creates a basic configuration file to control the `foo` service.
 
@@ -92,6 +92,6 @@ $ systemctl status foo
 Dec 14 14:09:12 dansmachine systemd[1]: Started My custom service.
 ----
 
-.Related Information
+== Related Information
 
 * See link:#common-service-parameters[Common service parameters] for more information about the parameters used in this procedure.

modules/ROOT/pages/_partials/proc_starting-stopping-and-querying-systemd-services.adoc

@@ -3,11 +3,11 @@
 
 You can perform various management tasks to control systemd services using the `systemctl` command. The following is a set of example commands to demonstrate how to use `systemctl` to manage systemd services.
 
-.Prerequisites
+== Prerequisites
 
 You are logged in as a user with administrator-level permissions.
 
-.Procedure
+== Procedure
 
 The following commands control the `foo` service:
 
@@ -59,6 +59,6 @@ The following commands control the `foo` service:
 # systemctl is-enabled foo
 ----
 
-.Related Information
+== Related Information
 
 * Run `man systemctl` for more details.

modules/ROOT/pages/_partials/ref_common-service-parameters.adoc

@@ -1,7 +1,7 @@
 [#common-service-parameters]
 = Common service parameters
 
-.Unit Parameters
+== Unit Parameters
 
 This section contains parameters you can use in the `[Unit]` section of a service. These parameters are common to other systemd units.
 
@@ -34,7 +34,7 @@ Before, After::
 OnFailure::
   A space-separated list of unit names that are activated when this service enters a failed state.
 
-.Install Parameters
+== Install Parameters
 
 This section contains parameters you can use in the `[Install]` section of a service. These parameters are common to other systemd units.
 
@@ -49,7 +49,7 @@ RequiredBy, WantedBy::
 Also::
     Additional units to install or uninstall when this service is installed or uninstalled.
 
-.Service Parameters
+== Service Parameters
 
 This section contains parameters you can use in the `[Service]` section of a service unit. These parameters are specific only to systemd service units.