improve api key and retry duration section

Signed-off-by: Kavindu Dodanduwa <kavindu.dodanduwa@elastic.co>

docs/en/observability/cloud-monitoring/aws/ingest-aws-firehose.asciidoc

@@ -55,11 +55,11 @@ NOTE: For advanced use cases, source records can be transformed by invoking a cu
 +
 * *Elastic endpoint URL*: Enter the {es} endpoint here. To find the {es} endpoint, go to the https://cloud.elastic.co/[Elastic Cloud] console, select your deployment and use *Copy endpoint* next to *Elasticsearch*. URL will have the format of: `https://<cluster-id>.es.<region>.<csp>.elastic-cloud.com`.
 +
-* *API key*: Enter the encoded Elastic API key. To create an API key, go to the Elastic Cloud console, select *Connection details* and click *Create and manage API keys*. If you are using an API key with *Restrict privileges*, make sure to review the Indices privileges to provide at least "auto_configure" & "write" permissions for the indices you will be using with this delivery stream.
+* *API key*: Enter the encoded Elastic API key. This can be created in Kibana by following the instructions under API Keys. If you are using an API key with Restricted privileges, be sure to review the Indices privileges to provide at least "auto_configure" & "write" permissions for the indices you will be using with this delivery stream.
 +
 * *Content encoding*: For a better network efficiency, leave content encoding set to GZIP.
 +
-* *Retry duration*: Determines how long Firehose continues retrying the request in the event of an error. A duration of 60-300s should be suitable for most use cases.
+* *Retry duration*: Determines how long Firehose continues retrying the request in the event of an error. A duration between 60 seconds to 300 seconds should be suitable for most use cases.
 +
 * *Parameters*:
 +