Skip to content

Commit bfad479

Browse files
authored
Fix/typos-unevaluated (#277)
couple typos in there Signed-off-by: Jeremy Fiel <[email protected]>
1 parent c73f94e commit bfad479

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

content/2020-12/unevaluated/unevaluatedProperties.markdown

+2-2
Original file line numberDiff line numberDiff line change
@@ -104,8 +104,8 @@ It's crucial to understand what evaluation means in this context.
104104
{ "keyword": "/patternProperties", "instance": "", "value": [ "bar" ] }
105105
{{</instance-annotation>}}
106106

107-
* For the first instace, the annotation result of `properties` is [ "foo" ], and the annotation result of `patternProperties` is [ "bar" ]. However, the 'fooBar' property remains unevaluated, so the `unevaluatedProperties` subschema applies to it. This subschema fails (as any instance against a false schema is always invalid), leading to the failure of the entire schema.
108-
* For the second instace, the annotation result of `properties` is [ "foo" ], and the annotation result of `patternProperties` is [ "bar" ]. No properties remain unevaluated; hence, the instance is considered valid.
107+
* For the first instance, the annotation result of `properties` is [ "foo" ], and the annotation result of `patternProperties` is [ "bar" ]. However, the 'fooBar' property remains unevaluated, so the `unevaluatedProperties` subschema applies to it. This subschema fails (as any instance against a false schema is always invalid), leading to the failure of the entire schema.
108+
* For the second instance, the annotation result of `properties` is [ "foo" ], and the annotation result of `patternProperties` is [ "bar" ]. No properties remain unevaluated; hence, the instance is considered valid.
109109

110110
{{<schema `Schema with 'unevaluatedProperties', 'properties', and 'patternProperties', with unevaluatedProperties set to an object subschema`>}}
111111
{

0 commit comments

Comments
 (0)