docs: docs: guide - default values cue

Add default values cue doc page + implement all maintainers suggestions

Signed-off-by: guillaume <guillaume.derouville@gmail.com>

docs/faq/1232-chain-actions.md

@@ -1,26 +1,23 @@
 ---
 slug: /1232/chain-actions
-displayed_sidebar: europa
+displayed_sidebar: '0.2'
 ---
 
-# Chaining actions
+# How can I chain actions together ?
 
 Dependencies are materialized at runtime, when your Cue files are parsed and the corresponding DAG gets generated:
 
 ```cue
 // Prerequisite action that runs when `test` is being called
 _dockerCLI: alpine.#Build & {
-    packages: {
-        bash: {}
-    }
+    packages: bash: _
 }
 
 // Main action
 foo: bash.#Run & {
     input: _dockerCLI.output // <== CHAINING of action happening here
-    always: true
     script: contents: #"""
-        echo "bonjour"
+        echo "hello"
         """#
 }
 ```
@@ -29,26 +26,24 @@ On above example, `_dockerCLI` gets executed first, as the corresponding DAG sho
 
 This is the `input-output` model: `foo`'s input is `_dockerCLI`'s output.
 
-We currently don't support explicit dependencies at the moment (one of our top priority). But, if you need one, here is how your can hack your way around it:
+We currently do not support explicit dependencies at the moment (one of our top priority). But, if you need one, here is how you can hack your way around it:
 
 ```cue
 foo: bash.#Run & {
     input: _dockerCLI.output
-    always: true
     script: contents: #"""
-        echo "bonjour"
+        echo "hello"
         """#
 }
 
 // Main action
 bar: bash.#Run & {
     input: _dockerCLI.output
-    always: true
     script: contents: #"""
-        echo "bonjour"
+        echo "hello"
         """#
     env: HACK: "\(test.success)" // <== HACK: CHAINING of action happening here
 }
 ```
 
-`foo` and `bar` are similar actions. I don't want to rely on the `input-output` model but still want to force a dependency between them. The easiest way is to create an environment variable that relies on the other action's success
+`foo` and `bar` are similar actions. If you do not want to rely on the `input-output` model but still want to force a dependency between them. The easiest way is to create an environment variable that relies on the other action's success