From 00b58146a2220265ab68f766d3efae885b3450f9 Mon Sep 17 00:00:00 2001
From: Chloe Kudryavtsev <toast@toastin.space>
Date: Thu, 7 Mar 2019 16:59:42 -0500
Subject: [style] Use standard XXX

MAINT -> COMBAK
---
 modules/Working/pages/openrc.adoc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'modules/Working/pages/openrc.adoc')

diff --git a/modules/Working/pages/openrc.adoc b/modules/Working/pages/openrc.adoc
index 3c617f9..7fdf56e 100644
--- a/modules/Working/pages/openrc.adoc
+++ b/modules/Working/pages/openrc.adoc
@@ -1,4 +1,4 @@
-// MAINT: openrc, whole page
+// COMBAK: openrc, whole page
 = Working with OpenRC
 
 OpenRC is the init system used in alpine.
@@ -14,7 +14,7 @@ If in doubt, use the canonical name, as is shown in this document.
 
 == Normal Usage
 === Manipulating Services
-// MAINT: openrc, whole page
+// COMBAK: openrc, whole page
 ==== Runtime Service Manipulation
 You manipulate services on a running system using the `rc-service` command.
 This allows you to start, stop, and check the status of a given service, amongst other things.
@@ -44,7 +44,7 @@ Only run the specified command if the service is currently started.
 
 NOTE: Services may define additional commands you can use. See more on this in <<_custom_service_commands>>.
 
-// MAINT: rc-update
+// COMBAK: rc-update
 ==== On-Boot Service Manipulation
 OpenRC operates under a system called "runlevels".
 More on that in <<_switching_runlevels>> and <<_custom_runlevels>>.
@@ -74,7 +74,7 @@ However, some services need configuration applied to them as part of the launch
 This can be done in the `/etc/conf.d` directory, under the name of the service in question.
 For example, for a service named "base", the configuration file would be `/etc/conf.d/base`.
 
-// MAINT: rc-status
+// COMBAK: rc-status
 === System Status
 The `rc-status` utility is a fast way to view the current state of your system's services.
 By default, it will list all the services in the current runlevel.
@@ -142,7 +142,7 @@ Their usage is identical to that of the built-in ones.
 You can look inside the `init.d` script at various `extra*commands` variables which give a listing of the available ones.
 // TODO: what's extra_started_commands etc?
 
-// MAINT: the insanity in sh/opnenrc-init.sh.in
+// COMBAK: the insanity in sh/opnenrc-init.sh.in
 === Extended `conf.d` Names
 There are 4 total files that may play a role in the configuration of a service.
 Assume that `base` stands for the name of the base server, `ext` is the extension (as per <<_multi_services>>) and `runlevel` is the runlevel it's in.
-- 
cgit v1.2.3

