Hello,

In Airflow 2, we've moved some configuration options to the new section. We also changed the names of some of the configuration options. This is confusing for users who are familiar with the old option and section names.  It would be great if we could add information to the documentation that points to the new name of the options.

https://github.com/apache/airflow/blob/8f48f12128e0d985c6de2603902524859fecbca8/airflow/configuration.py#L139-L169

> 'The {old} option in [{section}] has been renamed to {new}
> 'The {old_key} option in [{old_section}] has been moved to the {new_key} option in '
> '[{new_section}]

Best regards,
Kamil Breguła

docs/conf.py
# If this is True, viewcode extension will emit viewcode-follow-imported event to resolve the name of
# the module by other extensions. The default is True.
viewcode_follow_imported_members = True
# -- Options for sphinx-autoapi ------------------------------------------------
# 
# Paths (relative or absolute) to the source code that you wish to generate
# your API documentation from.
autoapi_dirs = [
    PACKAGE_DIR,
]
# A directory that has user-defined templates to override our default templates.
if PACKAGE_NAME == 'apache-airflow':
    autoapi_template_dir = 'autoapi_templates'
# A list of patterns to ignore when finding files
autoapi_ignore = [
    'airflow/configuration/',
    '*/example_dags/*',
    '*/_internal*',
    '*/node_modules/*',
    '*/migrations/*',
    '*/contrib/*',
]
if PACKAGE_NAME == 'apache-airflow':
    autoapi_ignore.append('*/airflow/providers/*')
# Keep the AutoAPI generated files on the filesystem after the run.
# Useful for debugging.
autoapi_keep_files = True
# Relative path to output the AutoAPI files into. This can also be used to place the generated documentation
# anywhere in your documentation hierarchy.
autoapi_root = f'{PACKAGE_NAME}/_api'