Add missing part + fix mentions of lintScript and prettyScript

Author: ZakaHaceCosas

docs/manual/fknode-yaml.md

@@ -106,7 +106,7 @@ commitMessage: "Automated maintenance commit by FuckingNode"
 
 ### updaterOverride
 
-Overrides the default command for the updating dependencies with the provided runtime script command. Works the same way as [lintCmd](#lintscript) or [prettyCmd](#prettyscript), we simply made the name more verbose because in most cases you don't need (and should not) mess around with it.
+Overrides the default command for the updating dependencies with the provided runtime script command. Works the same way as [lintScript](#lintscript) or [prettyScript](#prettyscript), we simply made the name more verbose because in most cases you don't need (and should not) mess around with it.
 
 - **Type**: `string`
 - **Example**:
@@ -212,11 +212,20 @@ It's something like this:
 { msft: ~Write-Host 'Hi from Windows!', posix: ~echo 'Hi from Linux/macOS!' }
 ```
 
-Info:
+All commands run in order and block each other. Also, colons are not required. Single and double colons are accepted. `~foo` is equal to `~"foo"` and  `~'foo'`.
 
-- All commands run in order and block each other.
-- Colons are not required. Single and double colons are accepted. `~foo` is equal to `~"foo"` and  `~'foo'`.
-- Cmd output is not live, meaning if a command writes to the stdout step by step, you won't see that until it ends execution.
+By default, output for each Cmd is not live; this is, invisible until the command ends execution. However, sometimes you might not want that, for example for a live server which "never terminates" and you might want to interact with (to refresh it, for example).
+
+If you want a command to be interactive, you may manually specify it as a _detached cmd_, by using the special `;;` prefix (between the Cmd key and the actual command).
+
+For example:
+
+```yaml
+launchCmd:
+  - $;;some-script
+```
+
+This will "detach" the script, allowing to interact with it. ++ctrl+c++-ing out of it will end the detached process and continue the sequence if any Cmd (detached or not) exists after it.
 
 You can use CmdSets for the following project settings:
 

docs/manual/usage.md

@@ -156,7 +156,7 @@ When linting, we will automatically run your linter. By default, we use ESLint -
 
 More precisely, `--lint` runs `eslint --fix .` on each of your projects, unless overridden.
 
-To override it, create a script in your `package.json` scripts object that runs your preferred linter, then copy the name of the script and paste it as the value for the `lintCmd` key on your `fknode.yaml`.
+To override it, create a script in your `package.json` scripts object that runs your preferred linter, then copy the name of the script and paste it as the value for the `lintScript` key on your `fknode.yaml`.
 
 For example:
 
@@ -167,7 +167,7 @@ scripts: {
 ```
 
 ```yaml title="fknode.yaml" linenums="1"
-lintCmd: "linter"
+lintScript: "linter"
 ```
 
 ### Prettifying your code
@@ -176,7 +176,7 @@ When prettying, we will automatically run your prettifier. By default, we use Pr
 
 More precisely, `--pretty` runs `prettier --w .` on each of your projects, unless overridden.
 
-To override it, do the same as with the linter but setting the `prettyCmd` key instead.
+To override it, do the same as with the linter but setting the `prettyScript` key instead.
 
 For example:
 
@@ -187,7 +187,7 @@ scripts: {
 ```
 
 ```yaml title="fknode.yaml" linenums="2"
-prettyCmd: "prettifier"
+prettyScript: "prettifier"
 ```
 
 ### Destroying your files