The generic configuration section of the Envoy documentation currently links only to the v2 APIs. What we need is a way, ideally driven by the type database information, to generate links to both v2 and v3 messages wherever we have a link. This might take the form of multiple bullet points where links are contained in bullet points, or an inline v2/v3 link alternative.