From 0e291946687a56edf8092bcc146f317b2070c9aa Mon Sep 17 00:00:00 2001 From: Phanupong Janthapoon Date: Tue, 18 Sep 2018 11:38:26 +0700 Subject: [PATCH] update misspelling on index.en-US.md (#12280) On the line 158, the words "can not" are likely in a wrong construction for this sentence. It would be better to use "cannot" in this context. --- components/form/index.en-US.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/form/index.en-US.md b/components/form/index.en-US.md index 0f7dada009..1ec4c259bb 100644 --- a/components/form/index.en-US.md +++ b/components/form/index.en-US.md @@ -155,7 +155,7 @@ To mark the returned fields data in `mapPropsToFields`, [demo](#components-form- After wrapped by `getFieldDecorator`, `value`(or other property defined by `valuePropName`) `onChange`(or other property defined by `trigger`) props will be added to form controls，the flow of form data will be handled by Form which will cause: 1. You shouldn't use `onChange` to collect data, but you still can listen to `onChange`(and so on) events. -2. You can not set value of form control via `value` `defaultValue` prop, and you should set default value with `initialValue` in `getFieldDecorator` instead. +2. You cannot set value of form control via `value` `defaultValue` prop, and you should set default value with `initialValue` in `getFieldDecorator` instead. 3. You shouldn't call `setState` manually, please use `this.props.form.setFieldsValue` to change value programmatically. #### Special attention