From 73c70e28b4301b63e53b1dbd5056bfcc17287926 Mon Sep 17 00:00:00 2001 From: MMeent Date: Tue, 21 May 2019 15:27:58 +0200 Subject: [PATCH] Clear up some inconsistent / unclear wording IPv6 enabled/disabled working was confusing or contradicting itself. This updates the wording to what is expected, based on the default values in the table above, and the behaviour that I could find in code. --- docs/user-guide/nginx-configuration/configmap.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/nginx-configuration/configmap.md b/docs/user-guide/nginx-configuration/configmap.md index 19d16f1b4..62c34e720 100755 --- a/docs/user-guide/nginx-configuration/configmap.md +++ b/docs/user-guide/nginx-configuration/configmap.md @@ -259,11 +259,11 @@ _References:_ ## disable-ipv6 -Disable listening on IPV6. _**default:**_ is disabled +Disable listening on IPV6. _**default:**_ `false`; IPv6 listening is enabled ## disable-ipv6-dns -Disable IPV6 for nginx DNS resolver. _**default:**_ is disabled +Disable IPV6 for nginx DNS resolver. _**default:**_ `false`; IPv6 resolving enabled. ## enable-underscores-in-headers