DRAFT docs, ch3 - elicitation

[softchris]

Purpose

Elicitation is about supporting a scenario where the user makes a first selection, for example a booking, and it's not available. The elicitation happens when the server asks the user to make a different choice and "elicits" a new response from the client.

Does this introduce a breaking change?

When developers merge from main and run the server, azd up, or azd deploy, will this produce an error? If you're not sure, try it out on an old environment.

[ ] Yes
[ ] No

Does this require changes to learn.microsoft.com docs or modules?

which includes deployment, settings and usage instructions.

[ ] Yes
[ ] No

Type of change

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

[leestott]

@softchris can you fix the suggestions provided Also changelog.md needs update Main readme.md need updating with new chapter context