fix issue #1210 in material.angular.io https://github.com/angular/ma…

[darpankumar]

This PR fix the issue issue 1210 in which autofilled property is not mentioned in the document along with this added another missing property documentation. Please let me know if any changes are require.

After fix document screenshot.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[DmitryEfimenko]

Thanks for the PR! I am happy to see the description of what would happen if the property autofilled is set to true or false.
However, I think there's still room for improvement in the following sentence:

This property allows us to specify Whether the input is currently in an autofilled state.

First, the word "Whether" should be lower-case.
Second, and most important - I still don't understand what would be the situation when a developer should set the autofilled property to true or false. Is it referring to the browser's autofill functionality? In that case, how can develop identify if the control was autofilled? Or is this referring to something else? A description of a concrete situation when this property should be set would be helpful.

[darpankumar]

Hi @DmitryEfimenko I will fix the word.
As per my understanding this is similar to the case where we mark a control touched/disabled. Similarly we need to implement this flag with true or false when the property is auto filled by the browser.