From 4c8337713f343a9250fb68601ecd0b5382482ece Mon Sep 17 00:00:00 2001
From: Greg Dennis <gregsdennis@yahoo.com>
Date: Thu, 26 May 2022 21:51:27 +1200
Subject: [PATCH] add clarification that minContains:0 also causes contains to
 pass

---
 jsonschema-validation.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml
index fdc3d4a4..ee3ee1b6 100644
--- a/jsonschema-validation.xml
+++ b/jsonschema-validation.xml
@@ -443,8 +443,8 @@
                     <t>
                         A value of 0 is allowed, but is only useful for setting a range
                         of occurrences from 0 to the value of "maxContains". A value of
-                        0 causes "minContains" to always pass validation (but validation can
-                        still fail against a "maxContains" keyword).
+                        0 causes "minContains" and "contains" to always pass validation
+                        (but validation can still fail against a "maxContains" keyword).
                     </t>
                     <t>
                         Omitting this keyword has the same behavior as a value of 1.