Work in progress

src/get-started/modules/ROOT/pages/configuration-policies/apply.adoc

@@ -1,5 +1,17 @@
 == Run agent locally
 
+[NOTE]
+
+====
+
+In this section you will:
+
+* Trigger a policy application locally on the node using Rudder CLI
+* Read the policy enforcement state in its output
+* Check reported compliance in the Web interface
+
+====
+
 Let's connect to our Rudder server by SSH:
 
 ----

src/get-started/modules/ROOT/pages/configuration-policies/directive.adoc

@@ -1,5 +1,16 @@
 == Use a predefined policy
 
+[NOTE]
+
+====
+
+In this section you will:
+
+* Define a configuration policy from a pre-defined template
+* Create appliable configuration items called *directives* from
+
+====
+
 You have just learnt to use the technique editor, which gives access to a broad
 range of building blocks for policies. To allow easy configuration of
 common system settings, Rudder also comes with a pre-defined set of techniques,

src/get-started/modules/ROOT/pages/configuration-policies/policy-mode.adoc

@@ -1,5 +1,16 @@
 == Audit vs. Enforce - Policy Mode
 
+[NOTE]
+
+====
+
+In this section you will:
+
+* Analyze results from an audit policy
+* Switch between audit and enforce modes to fix the configuration issues
+
+====
+
 As you saw just before, we configured one of our directives in "Audit mode".
 You may have guessed, according to its name, what this means.
 

src/get-started/modules/ROOT/pages/configuration-policies/technique.adoc

@@ -1,5 +1,16 @@
 == Define a configuration policy
 
+[NOTE]
+
+====
+
+In this section you will:
+
+* Use policy building blocks in the builder UI
+* Define a configuration policy within Rudder
+
+====
+
 Here you will learn to define a configuration policy through Rudder's technique editor.
 A technique is a configuration policy template, that will need to be instanciated afterwards.