Clarify that disabling kubernetes built in secret store can only be d…

…one with an annotation, not by setting a helm argument

Clarify that disabling kubernetes built in secret store can only be done with an annotation, not by setting a helm argument
Signed-off-by: James Bartlett <[email protected]>

Signed-off-by: james-bartlett <[email protected]>

daprdocs/content/en/developing-applications/building-blocks/secrets/secrets-overview.md

@@ -41,7 +41,7 @@ Applications can also use the secrets API to access secrets from a Kubernetes se
 - The Helm defaults, or
 - `dapr init -k`
 
-If you are using another secret store, you can disable (not configure) the Dapr Kubernetes secret store by setting `disable-builtin-k8s-secret-store` to `true` through the Helm settings. The default is `false`.
+If you are using another secret store, you can disable (not configure) the Dapr Kubernetes secret store by adding the annotation `dapr.io/disable-builtin-k8s-secret-store: "true"` to the deployment.yaml file. The default is `false`.
 
 In the example below, the application retrieves the same secret "mysecret" from a Kubernetes secret store.
 
@@ -86,4 +86,4 @@ Want to skip the quickstarts? Not a problem. You can try out the secret manageme
 ## Next steps
 
 - Learn [how to use secret scoping]({{< ref secrets-scopes.md >}}).
-- Read the [secrets API reference doc]({{< ref secrets_api.md >}}).
+- Read the [secrets API reference doc]({{< ref secrets_api.md >}}).