Merge pull request #22128 from danielorihuela/docs/update-secrets-providers-field-name

docs: update secrets providers field name

Author: PallaviWrite

src/content/docs/new-relic-control/agent-control/configuration.mdx

@@ -433,7 +433,7 @@ Agent Control provides a robust mechanism for managing sensitive data, such as p
 ### Defining Secrets in Configuration
 To utilize secrets, define them within your Agent Control configuration YAML file by following these steps:
 
-1. **Define the `secrets_providers` section:** Configure your secret providers centrally in this section. Ensure each entry corresponds to a supported provider.
+1. **Define the `secretsProviders` section:** Configure your secret providers centrally in this section. Ensure each entry corresponds to a supported provider.
 2. **Configure secret sources:** For each provider, specify one or more sources. A source includes the necessary configuration details (for example, URL, token) for Agent Control to connect to and retrieve a group of secrets.
 3. **Use placeholders in agent configurations:** Instead of the actual sensitive data, use a placeholder string within your agent's configuration. Agent Control automatically replaces these placeholders with the retrieved secrets during the rendering process.
 
@@ -444,7 +444,7 @@ To utilize secrets, define them within your Agent Control configuration YAML fil
 The following Agent Control configuration example demonstrates how to retrieve secrets from two Vault sources within the `secrets_providers` section:
 
 ```yaml
-secrets_providers:
+secretsProviders:
   vault:
     sources:
       local-instance: