Inconsistencies in YAML config docs

[thomas11]

Problem description

I noticed a few inconsistencies in our YAML docs about the project-level config.

• Pulumi YAML reference right at the top links to config options, which says that the type property can be “either string, boolean, integer, or array.” But the “Config” section on Pulumi YAML reference says “It can be one of: String, Number, List, or List.”
  • Note the capitalization, too.
• Also, config options lists type as required whereas Pulumi YAML reference doesn’t (“Either type or default is required.“). Nevertheless the description says “Type is the (required) data type …”
• The “Config” section on Pulumi YAML reference doesn’t mention the variant where a config key maps directly to a value (foo: bar) instead of a structured object, which is documented on config options.

Suggestions for a fix

Apart from fixing the issues above, I wonder if we could avoid having two sections on config on two different pages? It's YAML either way.