Tell people that mixing V1 and V2 config files in the same project (note: even outside the gen2 function) will create a port and container error. Right now you don't mention in the docs or anywhere that having ANY function.config files in a project with a gen 2 function will cause a deploy error that says a container is broken and the port is unreachable. This error is misleading. It will also show the gen 2 function in the console as "unknown trigger" which also is misleading.

In all your documentation you say you can have gen1 and gen2 functions in the same project, but you don't warn people that using function.config configs OUTSIDE of the gen2 functions will still kill the deploy. This makes mixing gen 1 and gen2 functions essentially impossible for anyone who uses gen1 config variables, which is probably most people.

A quick google search will show that many people have this problem so the error should either be fixed or it should be noted in the upgrade documentation.