Configuring-Policies.md

@@ -2,7 +2,7 @@ A traffic policy specifies what kind of treatment should be applied to user traf
 
 ```
 Heimdall > config policy my_little_policy
-Heimdall config policy my_little_policy > set rule 10 route-via tunnel/69
+Heimdall config policy my_little_policy > add rule 10 route-via tunnel/69
 Heimdall config policy my_little_policy > show
 ===============================================================================
 5: loadbalance some-map
@@ -12,4 +12,9 @@ Heimdall config policy my_little_policy > show
 
 Policies are applied in the priority order, ergo it is a good idea to "leave" space in between priority numbers so that you can insert rules in between later if need be.
 
-Note that there are plans to support further actions (like copy and forward or packet marks) etc and to have ACLs associated with rules, so that each rule applies only to a specific type of traffic (Work in Progress®)
+Currently, the following actions are supported when configuring a policy:
\ No newline at end of file
+
+- **loadbalance**: Perform traffic loadbalancing over a route-map
+- **route-via**: <interface name to route traffic out on>
+- **discard**: Drop traffic
+- **continue**: Return traffic to the Linux routing stack for further regular processing