The current documentation for installing dynamic plugins in air-gapped environments (Section 1.3) is incomplete https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.6/html/installing_and_viewing_plugins_in_red_hat_developer_hub/rhdh-installing-rhdh-plugins_title-plugins-rhdh-about#proc-install-plugins-using-custom-npm-registry

The airgapped installation shows creating a secret with .npmrc but ends without explaining:
what to do after creating the Secret
How to reference it in the Backstage CR or Helm values

Also section 1.2.1. Example Helm chart configurations for dynamic plugin installations, the two examples are identical:
Enabling a plugin from an included file
Enabling a plugin that is disabled in an included file
Both show the same YAML with disabled: false and reference dynamic-plugins.custom.yaml, making them redundant.

Acceptance criteria:

– have two distinguished airgapping processes for installing dynamic-plugins in airgapped environments for helm and the operator.

--remove redundancy within section 1.2.1