doc fix

doc/disable.md

@@ -23,7 +23,7 @@ The `66 -t` command option have no effect. `66` will detect automatically the as
 
 In case of `module` service type, all services within the `module` are disabled.
 
-Multiple *services* can be disabled by seperating their names with a space.
+Multiple *services* can be disabled by separating their names with a space.
 
 This command handles [interdependencies](66.html#handling-dependencies).
 

doc/enable.md

@@ -19,11 +19,11 @@ enable [ -h ] [ -S ] service...
 
 This command will also parse the service if it was never parsed. The *service* will then be available in the given *tree* for the next boot depending on the state of the *tree*. The targeted service(s) can also be started on the fly when enabling it with the **-S** option.
 
-The given *tree* can be define through the `-t` option in the `66` general option or by using the `@intree` field within the frontend file or setting a current tree through the [66 tree current](66-tree.html) subcommand. If neither `-t` options nor `@intree` is provided, or if no tree is marked as a current one, it will enable the service within the default tree named `%%default_treename%%`. The default tree name can be changed at compile time by passing the `--with-default-tree-name` to `./configure`.
+The given *tree* can be define through the `-t` option in the `66` general option or by using the `@intree` field within the frontend file or setting a current tree through the [66 tree current](tree.html#current) subcommand. If neither `-t` options nor `@intree` is provided, or if no tree is marked as a current one, it will enable the service within the default tree named `%%default_treename%%`. The default tree name can be changed at compile time by passing the `--with-default-tree-name` to `./configure`.
 
 In case of `module` service type, all services within the `module` are enabled.
 
-Multiple *services* can be enabled by seperating their names with a space.
+Multiple *services* can be enabled by separating their names with a space.
 
 This command handles [interdependencies](66.html#handling-dependencies).
 

doc/init.md

@@ -28,7 +28,7 @@ The command `66 scandir create` need to be executed before trying to run the `in
 
 The command will make an exact copy of the *enabled* service files and directories of the *tree* inside a [scandir](scandir.html) directory at `%%livedir%%/state/UID` where *UID* is the uid of the current owner of the process. The [scandir](scandir.html) does not need to be necessarily running. This is useful at boot time to initiate an early service before starting the scandir. Once the [scandir](scandir.html) starts—see [66 scandir start](scandir.html) command, the already present services start automatically.
 
-If the [scandir](scandir.html) is running, you should invoke a [66 scandir reconfigure](scandur.html) command to inform it about the changes.
+If the [scandir](scandir.html) is running, you should invoke a [66 scandir reconfigure](reconfigure.html) command to inform it about the changes.
 
 ## Note
 

doc/reconfigure.md

@@ -23,7 +23,7 @@ If the *service* is running, it is stopped and then unsupervised. Afterward, the
 
 For `module` *service* types, the same process is applied to all services within the *module*. If the module is part of a tree associated with the boot [group](tree.html#groups-behavior), only the parse process is executed to avoid interrupting the boot sequence. The changes will be applied during the next [reboot](reboot.html).
 
-Multiple *services* can be disabled by seperating their names with a space.
+Multiple *services* can be disabled by separating their names with a space.
 
 This command handles [interdependencies](66.html#handling-dependencies) for the [stop](stop.html), [free](free.html) and [start](start.html) process.
 

doc/reload.md

@@ -23,7 +23,7 @@ The `66 -t` command option have no effect. `66` will detect automatically the as
 
 In case of `module` service type, all services within the `module` are reloaded.
 
-Multiple *services* can be reloaded by seperating their names with a space.
+Multiple *services* can be reloaded by separating their names with a space.
 
 This command handles [interdependencies](66.html#handling-dependencies).
 

doc/resolve.md

@@ -19,7 +19,7 @@ resolve [ -h ] service
 
 This command displays the contents of the service's *resolve* file. This file are used internally by the `66` program to know *service* information. This command is purely a debug command used by system administrators or developers.
 
-[Resolve](deeper.html#Resolve-files) files are at the core of `66` for service information. They are used internally by `66` to build the dependency graph, ascertain file locations, the parse process result of a service, and other critical aspects of a service.
+[Resolve](deeper.html#resolve-files) files are at the core of `66` for service information. They are used internally by `66` to build the dependency graph, ascertain file locations, the parse process result of a service, and other critical aspects of a service.
 
 ## Options
 

doc/restart.md

@@ -14,7 +14,7 @@ This command restarts one or more services.
 ## Interface
 
 ```
-restart [ -h ] [ -P ] service(s)
+restart [ -h ] [ -P ] service...
 ```
 
 This command bring down and bring up again a *service*. This command expects to find an already running *service*.
@@ -23,7 +23,7 @@ The `66 -t` command option have no effect. `66` will detect automatically the as
 
 In case of `module` service type, all services within the `module` are restarted.
 
-Multiple *services* can be disabled by seperating their names with a space.
+Multiple *services* can be disabled by separating their names with a space.
 
 This command handles [interdependencies](66.html#handling-dependencies).
 

doc/start.md

@@ -14,12 +14,12 @@ This command starts one ore more *services*.
 ## Interface
 
 ```
-start [ -h ] [ -P ] service(s)
+start [ -h ] [ -P ] service...
 ```
 
 This command expects to find an already running [scandir](scandir.html). If the state of the *service* is already up, the *start* command does nothing but handles dependency except when passing the `-P` option.
 
-Multiple *services* can be started by seperating their names with a space.
+Multiple *services* can be started by separating their names with a space.
 
 If the *service* has never been parsed, the *start* command will parse it and associate the service with a specific *tree* if the `66 -t` option was used, or if the `frontend` file defines the `@intree` field, or if a `tree` was marked as current—refer to the [tree current](tree.html) subcommand. Otherwise, the *service* will be associated with the `%%default_treename%%`. This process is applied to all dependencies of the service.
 

doc/stop.md

@@ -14,12 +14,12 @@ This command stops one ore more *services*.
 ## Interface
 
 ```
-stop [ -h ] [ -P ] service(s)
+stop [ -h ] [ -P ] service...
 ```
 
 This command expects to find an already running [scandir](scandir.html) and an already parsed service. If the state of the *service* is already down, the *stop* command does nothing but handles required-by dependency except when passing the `-P` option.
 
-Multiple *services* can be stopped by seperating their names with a space.
+Multiple *services* can be stopped by separating their names with a space.
 
 The `66 -t` command option have no effect. `66` will detect automatically the associated *tree* of the service along its required-by dependencies.
 

doc/upgrade.md

@@ -22,12 +22,12 @@ This release marks a significant rewrite of `66`, introducing a new UI and servi
 
 Primarily, expect no compatibility with previous versions due to:
 
-- The removal of `s6-rc` support. Service management is now fully integrated into `66`.
+- The removal of `s6-rc` support. `66` is now a complete independent service management based on s6 for init and service supervision.
 - A complete overhaul of the folder structure for storage and runtime directories, simplifying it considerably.
 - An overhaul of tree behavior. Trees now function as services, and a complete tree dependency graph has been implemented.
 - Services can now depend on each other regardless of whether the service is declared on the same tree or the declaration order of the tree. For instance, if service `Sb` depends on service `Sa` and `Sa` is within `TreeB` while service `Sb` is within `TreeA`, and `TreeB` depends on `TreeA`, launching `TreeA` will start `Sa` even if `TreeB` isn't started first. When `TreeB` is executed, `Sb` will find `Sa` already started and commence directly.
 
-For UI changes, a [Rosetta stone](#rosetta.md) is available.
+For UI changes, frontend file convertion and clean of the `66` architecture, a [Rosetta stone](#rosetta.md) is available.
 
 ## Frontend Files
 
@@ -47,14 +47,14 @@ Frontend files for regular account **must be** now localized at `%%service_syste
 
 - `@options`:
     - `pipeline`: This option was removed. It was only present for `s6-rc`.
-    - `env`: This option was removed. The simple declaration of the [environment] section.
+    - `env`: This option was removed. The simple declaration of the [environment] section is sufficient to activate the options.
 
-- `@shebang`: Deprecated but kept for compatibility reasons. Declare your shebang directly within the `@execute` field.
+- `@shebang`: Deprecated but kept for compatibility reasons. Declare your shebang directly within the `@execute` field. Refers to [frontend](frontend.html#a-word-about-the-@execute-key) documentation for futhers information.
 
 - `@build`: Not mandatory anymore, as it will be declared 'auto' by default.
-Service Behavior
 
-- `@addservices`
+- `@addservices`: This options was removed from the `[regex]` section.
+
 The `classic` type now accepts the fields `@depends` and `@requiredby`. The `classic` type replaces the `longrun` type.
 
 Logger destinations for `oneshot` type services can now be declared on a **tmpfs** directory, particularly useful during boot time.
@@ -65,7 +65,7 @@ The `bundle` and `longrun` types have been removed, replaced by `classic`, `ones
 
 ## [Environment] Section
 
-This section now allows reusing the same variable or variable from the actual environment. For instance:
+This section now allows reusing the same variable from the actual environment. For instance:
 
 ```
 socket_name=!/run/dbus/system_bus_socket