Fix swapped default values of adaptive.start and adaptive.end timeouts

While here, enlist start before end to restore intuitive order.

Spotted by someone on IRC who's name I cannot recall, sorry.
OK sashan

1 files changed, 8 insertions, 8 deletions

diff --git a/share/man/man5/pf.conf.5 b/share/man/man5/pf.conf.5
index a17fb795bb8..452a15d1cfd 100644
--- a/share/man/man5/pf.conf.5
+++ b/share/man/man5/pf.conf.5
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: pf.conf.5,v 1.581 2019/08/30 17:51:47 jmc Exp $
+.\"	$OpenBSD: pf.conf.5,v 1.582 2019/10/23 23:02:55 kn Exp $
 .\"
 .\" Copyright (c) 2002, Daniel Hartmeier
 .\" Copyright (c) 2003 - 2013 Henning Brauer <henning@openbsd.org>
@@ -28,7 +28,7 @@
 .\" ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: August 30 2019 $
+.Dd $Mdocdate: October 23 2019 $
 .Dt PF.CONF 5
 .Os
 .Sh NAME
@@ -1492,16 +1492,16 @@ Timeout values can be reduced adaptively as the number of state table
 entries grows.
 .Pp
 .Bl -tag -width Ds -compact
-.It Cm adaptive.end Pq 60000 states by default
-When reaching this number of state entries, all timeout values become
-zero, effectively purging all state entries immediately.
-This value is used to define the scale factor; it should not actually
-be reached (set a lower state limit, see below).
-.It Cm adaptive.start Pq 120000 states by default
+.It Cm adaptive.start Pq 60000 states by default
 When the number of state entries exceeds this value, adaptive scaling
 begins.
 All timeout values are scaled linearly with factor
 (adaptive.end \- number of states) / (adaptive.end \- adaptive.start).
+.It Cm adaptive.end Pq 120000 states by default
+When reaching this number of state entries, all timeout values become
+zero, effectively purging all state entries immediately.
+This value is used to define the scale factor; it should not actually
+be reached (set a lower state limit, see below).
 .El
 .Pp
 Adaptive timeouts are enabled by default, with an adaptive.start value