fixup! docs: ci: Update error handling

Signed-off-by: Jorge Marques <[email protected]>

Author: gastmaier

docs/ci.rst

@@ -93,10 +93,6 @@ These rules ensure that the downstream jobs do not run on fatal errors.
 Optional steps may also set ``fatal`` job-scoped environment variable, if taking
 care of calling ``set_step_fail``.
 
-The draw back of this approach is that captured/unexpected errors may have a step
-exit with error without set the set_step_fail, causing the step fail to fail through
-and passing the immediate assert step.
-
 Checking steps description
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -136,7 +132,7 @@ The checkers are, followed by which step event they raise:
   - | ``sparse``: the changed files are touched and recompiled with ``C=1``.
     | ``fail``: ``error`` logged
     | ``warn``: ``warning`` logged
-  - | ``ggc fanalyzer``: the changed files are recompiled appending the ``-fanalyzer`` flag.
+  - | ``gcc fanalyzer``: the changed files are recompiled appending the ``-fanalyzer`` flag.
     | It uses the *compile_commands.json* file to extract the correct compilation flags.
     | ``fail``: ``error`` or ``warning`` logged
   - | ``smatch``: the changed files are touched and recompiled with ``C=1 CHECK="smatch -p=kernel"``.