From 035cd809dc592d8f3778db43460fadbc8b701544 Mon Sep 17 00:00:00 2001 From: Michael Vera Date: Wed, 8 Jul 2015 15:07:27 -0400 Subject: [PATCH] Fix documentation typo --- docs/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/index.md b/docs/index.md index 99bc998cc..40db0478c 100644 --- a/docs/index.md +++ b/docs/index.md @@ -417,7 +417,7 @@ error code, so to specify a error message you also need to use. [ { key: 'name', - validationMessages: { + validationMessage: { 'noBob': 'Bob is not OK! You here me?' }, $validators: { @@ -441,7 +441,7 @@ a promise that resolves or rejects. [ { key: 'name', - validationMessages: { + validationMessage: { 'noBob': 'Bob is not OK! You here me?' }, $asyncValidators: { @@ -467,7 +467,7 @@ Form defaults in schema Its recommended to split presentation and validation into a form definition and a json schema. But if you for some reason can't do this, but *do* have the power to change the schema, you can supply form default values within the schema using the custom attribute `x-schema-form`. `x-schema-form` should -be a form object and acts as form definition defaults for that field. +be a form object and acts as form definition defaults for that field. Example schema. ```js