4 files changed, 18 insertions, 26 deletions
diff --git a/docs/configuration/loadbalancing/haproxy.rst b/docs/configuration/loadbalancing/haproxy.rst
index b29f9620..c7c25783 100644
--- a/docs/configuration/loadbalancing/haproxy.rst
+++ b/docs/configuration/loadbalancing/haproxy.rst
@@ -57,6 +57,16 @@ Service
   For an explanation on :ref:`syslog_facilities` and :ref:`syslog_severity_level`
   see tables in syslog configuration section.
 
+.. cfgcmd:: set load-balancing haproxy service <name> http-compression algorithm
+  <gzip | deflate | identity | raw-deflate>
+
+  Set the compression algorithm to be used when compressing HTTP responses.
+
+.. cfgcmd:: set load-balancing haproxy service <name> http-compression mime-type
+  <mime-type>
+
+  Set the list of HTTP response MIME types which haproxy will attempt to
+  compress, if received uncompressed from backend server.
 
 Rules
 ^^^^^
diff --git a/docs/configuration/nat/nat44.rst b/docs/configuration/nat/nat44.rst
index 68854c16..fb0d5af9 100644
--- a/docs/configuration/nat/nat44.rst
+++ b/docs/configuration/nat/nat44.rst
@@ -585,7 +585,7 @@ rule, using ``connection-status`` matcher:
 
   set firewall ipv4 forward filter rule 10 action accept
   set firewall ipv4 forward filter rule 10 connection-status nat destination
-  set firewall ipv4 forward filter rule 10 state new enable
+  set firewall ipv4 forward filter rule 10 state new
 
 This would generate the following configuration:
 
@@ -599,9 +599,7 @@ This would generate the following configuration:
                   connection-status {
                       nat destination
                   }
-                  state {
-                      new enable
-                  }
+                  state new
               }
           }
       }
diff --git a/docs/configuration/system/flow-accounting.rst b/docs/configuration/system/flow-accounting.rst
index 801ddae6..a339df75 100644
--- a/docs/configuration/system/flow-accounting.rst
+++ b/docs/configuration/system/flow-accounting.rst
@@ -7,8 +7,8 @@ Flow Accounting
 VyOS supports flow-accounting for both IPv4 and IPv6 traffic. The system acts
 as a flow exporter, and you are free to use it with any compatible collector.
 
-Flows can be exported via two different protocols: NetFlow (versions 5, 9 and
-10/IPFIX) and sFlow. Additionally, you may save flows to an in-memory table
+Flows can be exported via protocol NetFlow (versions 5, 9 and
+10/IPFIX). Additionally, you may save flows to an in-memory table
 internally in a router.
 
 .. warning:: You need to disable the in-memory table in production environments!
@@ -144,26 +144,6 @@ NetFlow
    If you want to change the maximum number of flows, which are tracking
    simultaneously, you may do this with this command (default 8192).
 
-sFlow
-^^^^^
-
-.. cfgcmd:: set system flow-accounting sflow server <address>
-
-   Configure address of sFlow collector. sFlow server at `<address>` can
-   be an IPv4 or IPv6 address. But you cannot export to both IPv4 and
-   IPv6 collectors at the same time!
-
-.. cfgcmd:: set system flow-accounting sflow sampling-rate <rate>
-
-   Enable sampling of packets, which will be transmitted to sFlow collectors.
-
-.. cfgcmd:: set system flow-accounting sflow agent-address <address>
-
-   Configure a sFlow agent address. It can be IPv4 or IPv6 address, but you
-   must set the same protocol, which is used for sFlow collector addresses. By
-   default, using router-id from BGP or OSPF protocol, or the primary IP
-   address from the first interface.
-
 Example:
 --------
 
diff --git a/docs/configuration/system/sflow.rst b/docs/configuration/system/sflow.rst
index 0c8bf03b..926d667b 100644
--- a/docs/configuration/system/sflow.rst
+++ b/docs/configuration/system/sflow.rst
@@ -44,6 +44,10 @@ Configuration
 
    Configure address of sFlow collector. sFlow server at <address> can be both listening on an IPv4 or IPv6 address.
 
+.. cfgcmd:: set system sflow enable-egress
+
+   Use this command to if you need to sample also egress traffic
+
 
 Example
 =======