Apply suggestion from @alicejgibbons

Co-authored-by: Alice Gibbons <[email protected]>
Signed-off-by: Mirel <[email protected]>

Author: MyMirelHub

daprdocs/content/en/reference/components-reference/supported-secret-stores/aws-secret-manager.md

@@ -45,7 +45,7 @@ The above example uses secrets as plain strings. It is recommended to use a loca
 | accessKey          | Y        | The AWS Access Key to access this resource                              | `"key"`             |
 | secretKey          | Y        | The AWS Secret Access Key to access this resource                       | `"secretAccessKey"` |
 | sessionToken       | N        | The AWS session token to use                                            | `"sessionToken"`    |
-| multipleKeyValuesPerSecret | N | `"true"` sets the multipleKeyValuesPerSecret behavior. Allows parsing JSON objects stored as secrets into multiple key-value pairs. Defaults to `"false"` | `"true"` |
+| multipleKeyValuesPerSecret | N | When set to `"true"` allows for multiple key value pairs to be stored in a single secret. Defaults to `"false"` | `"true"` |
 
 {{% alert title="Important" color="warning" %}}
 When running the Dapr sidecar (daprd) with your application on EKS (AWS Kubernetes), if you're using a node/pod that has already been attached to an IAM policy defining access to AWS resources, you **must not** provide AWS access-key, secret-key, and tokens in the definition of the component spec you're using.