doc update

doc/66-boot.md

@@ -21,7 +21,7 @@ This program performs some early preparations, spawns a process that will run th
 
 ## Exit codes
 
-*66-boot* never exits. It spawns the *rc.init* script and execs into [66‑scandir](66-scandir.html) which runs forever until the machine stops or reboots.
+*66-boot* never exits. It spawns the `rc.init` script and execs into [66‑scandir](66-scandir.html) which runs forever until the machine stops or reboots.
 
 ## Options
 
@@ -143,5 +143,5 @@ The following skeleton files are called to execute their corresponding power rel
 Any valid `key=value` pair set at the `init.conf` skeleton file can be passed on the kernel command line as parameter:
 
 ```
-    BOOT_IMAGE=../vmlinuz-linux root=/dev/sda3 ro vga=895 initrd=../intel-ucode.img,../initramfs-linux.img TREE=boot
+    BOOT_IMAGE=../vmlinuz-linux root=/dev/sda3 ro vga=895 initrd=../intel-ucode.img,../initramfs-linux.img TREE=boot VERBOSITY=4
 ```

doc/66-dbctl.md

@@ -16,11 +16,11 @@ This command is used to control an already supervised *service* in *live* define
 ```
 *66-dbctl* expects to find an already supervised *service* in *live* defined in the given *tree* and an already running *scandir*.
 
-**(!)** This tool **only** deals with **'bundle'** and **'atomic'** services—for *'classic'* services see [66-svctl](66-svctl.html).
+**(!)** This tool **only** deals with `bundle`, `module` and `atomic` services—for `classic` services see [66-svctl](66-svctl.html).
 
 Multiple *services* can be handled by separating their names with a space. *66-dbctl* gathers the services passed as argument in a list called *selection*.
 
-If *service* is not given, *66-dbctl* deals with all **'atomic'** services of the given *tree*.
+If *service* is not given, *66-dbctl* deals with all `bundle`, `module` and `atomic` services of the given *tree*.
 
 ## Exit codes
 

doc/66-disable.md

@@ -43,4 +43,4 @@ Multiple *services* can be disabled by seperating their names with a space.
 
 ## Dependencies handling
 
-In case of `'bundle'` or `'atomic'` services, any dependency chain will be automatically resolved. It is unnecessary to manually define chained sets of dependencies. If FooA has a declared dependency on FooB, FooB will be automatically disabled as well when disabling FooA. This will run recursively until all dependencies are disabled.
+In case of `bundle`, `module` or `'atomic'` services, any dependency chain will be automatically resolved. It is unnecessary to manually define chained sets of dependencies. If FooA has a declared dependency on FooB, FooB will be automatically disabled as well when disabling FooA. This will run recursively until all dependencies are disabled.

doc/66-enable.md

@@ -59,7 +59,7 @@ Multiple *services* can be enabled by seperating their names with a space.
 
 ## Dependency handling
 
-For *services* of type `bundle` or `atomic` any existing dependency chain will be automatically resolved. It is unnecessary to manually define chained sets of dependencies. If FooA has a declared dependency on another service with the name FooB then FooB will be automatically enabled too when enabling FooA. This works recursively until all necessary dependencies are enabled.
+For *services* of type `bundle`, `module` or `atomic` any existing dependency chain will be automatically resolved. It is unnecessary to manually define chained sets of dependencies. If FooA has a declared dependency on another service with the name FooB then FooB will be automatically enabled too when enabling FooA. This works recursively until all necessary dependencies are enabled.
 
 ## Directory name as service
 

doc/66-tree.md

@@ -89,5 +89,5 @@ As an example for root the resulting files would, by default, be found at `%%sys
 
 When you ask to start all *services* of the currently enabled tree at once with the [66-all](66-all.html) tool, the directory `%%system_dir%%/system/tree/servicedirs/svc` is opened and the command will start any *service* found inside of that directory.
 
-For *services* of type `bundle` and `atomic`, instead of opening the directory `%%system_dir%%/system/tree/servicedirs/db/source`, the corresponding compiled database found at `%%system_dir%%/system/tree/servicedirs/db/tree` is used. The database found at this location is the result of an automatic use of the command [s6-rc-compile](https://skarnet.org/software/s6-rc/s6-rc-compile.html) when enabling such a *service*. 
+For *services* of type `bundle`,`module` and `atomic`, instead of opening the directory `%%system_dir%%/system/tree/servicedirs/db/source`, the corresponding compiled database found at `%%system_dir%%/system/tree/servicedirs/db/tree` is used. The database found at this location is the result of an automatic use of the command [s6-rc-compile](https://skarnet.org/software/s6-rc/s6-rc-compile.html) when enabling such a *service*. 
 

doc/frontend.md

@@ -248,11 +248,11 @@ This section is *mandatory*. (!)
 
     valid values :
 
-    * classic : declares the service as classic.
-    * bundle : declares the service as a bundle service.  
-    * longrun : declares the service as a longrun service.
-    * oneshot : declares the service as a oneshot service.
-    * module : declares the service as a module service.
+    * classic : declares the service as a `classic` service.
+    * bundle : declares the service as a `bundle` service.  
+    * longrun : declares the service as a `longrun` service.
+    * oneshot : declares the service as a `oneshot` service.
+    * module : declares the service as a `module` service.
 
     **Note**: If you don't care about dependencies between services or if you don't need specific tasks or alternative configuration to get the daemon running, "classic" is the best pick.