I'm submitting a...
[x ] Documentation issue or request
Current behavior
The text in the docs does not match the example code given
Expected behavior
They should match
Minimal reproduction of the problem with instructions

The following format message in the component template binds to the component's gender property, which outputs one of the following string values: "m", "f" or "o". The message maps those values to the appropriate translations:
Referring to the example:
The author is {gender, select, male {male} female {female} other {other}}
What is the motivation / use case for changing the behavior?
Unless I am quite confused, it seems like the component should be said to be outputting "male", "female" or "other". If I am confused, then perhaps the docs should be clearer here..
Suggested new docs text:
The following format message in the component template binds to the component's gender property, which outputs one of the following string values: "male", "female" or "other". The message maps those values to the appropriate translations:
I'm submitting a...
[x ] Documentation issue or request
Current behavior
The text in the docs does not match the example code given
Expected behavior
They should match
Minimal reproduction of the problem with instructions
The following format message in the component template binds to the component's gender property, which outputs one of the following string values: "m", "f" or "o". The message maps those values to the appropriate translations:
Referring to the example:
What is the motivation / use case for changing the behavior?
Unless I am quite confused, it seems like the component should be said to be outputting "male", "female" or "other". If I am confused, then perhaps the docs should be clearer here..
Suggested new docs text:
The following format message in the component template binds to the component's gender property, which outputs one of the following string values: "male", "female" or "other". The message maps those values to the appropriate translations: