Graphql tool input parameter tables are less readable

[anupama-pathirage]

Description

$subject in https://ballerina.io/learn/graphql-tool/

For example consider the parameter mode.

In the Command options table at the top it is linking to 3 sub sections based on the usage. See below.

Then when we click on one such link, lets say Client generation it shows another table. Then under the possible values for the mode it shows all the three possible values where service and schema are not relevant for this sub section. See below.

My suggestion.

If we really want to have these sub tables, ideally the Command options table at the top should list all the possible values (i.e. client, service, schema for mode) while the sub tables, like Client generation should only show the values applicable for that sub section only. (i.e. client for mode)