From d0be8094ecf82dd6952780bb3d7a231eba5f3ba5 Mon Sep 17 00:00:00 2001 From: fpicalausa Date: Sat, 5 Feb 2022 03:02:01 +0900 Subject: [PATCH] docs: fix typo in discriminator documentation (#1885) --- docs/json-schema.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/json-schema.md b/docs/json-schema.md index e94e3226b..ac2d82d84 100644 --- a/docs/json-schema.md +++ b/docs/json-schema.md @@ -991,7 +991,7 @@ From the perspective of validation result `discriminator` is defined as no-op (t There are following requirements and limitations of using `discriminator` keyword: - `mapping` in discriminator object is not supported. - [oneOf](#oneof) keyword must be present in the same schema. -- discriminator property should be [requried](#required) either on the top level, as in the example, or in all `oneOf` subschemas. +- discriminator property should be [required](#required) either on the top level, as in the example, or in all `oneOf` subschemas. - each `oneOf` subschema must have [properties](#properties) keyword with discriminator property. The subschemas should be either inlined or included as direct references (only `$ref` keyword without any extra keywords is allowed). - schema for discriminator property in each `oneOf` subschema must be [const](#const) or [enum](#enum), with unique values across all subschemas.