Fix typo asyncInvoke => asyncInvocation

Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>

Author: alexellis

_posts/2021-08-02-openfaas-kafka-aiven.md

@@ -267,9 +267,9 @@ We've now set up a managed Kafka broker using Aiven and configured OpenFaaS Pro
 
 * How does this scale? Well you can set up the Kafka connector to listen to multiple topics by changing the `overrides.yaml` file such as: `topics: "signup,churn,quote-requested,quote-completed"` and each function can also subscribe to multiple topics.
 
-* If you have functions which are long-running, you can have them run in the background using the `asyncInvoke` setting for the Kafka connector, with this in place, all messages are dispatched to OpenFaaS' built-in NATS queue for processing when there is capacity available.
+* If you have functions which are long-running, you can have them run in the background using the `asyncInvocation` setting for the Kafka connector, with this in place, all messages are dispatched to OpenFaaS' built-in NATS queue for processing when there is capacity available.
 
-* What about retries? If you enable the `asyncInvoke` behaviour of the connector, and are an OpenFaaS Pro customer, then messages can be retried with an exponential back-off.
+* What about retries? If you enable the `asyncInvocation` behaviour of the connector, and are an OpenFaaS Pro customer, then messages can be retried with an exponential back-off.
 
 * What if I use [Confluent Cloud](https://www.confluent.co.uk/confluent-cloud/) or self-hosted Apache Kafka? You can also use SALS authentication if you're a [Confluent Cloud](https://www.confluent.co.uk/confluent-cloud/) customer, or bypass authentication if you run Kafka on a private network and are self-hosting the service.
 

_posts/2023-09-18-confluent-kafka.md

@@ -343,7 +343,7 @@ So if the `faas-request` topic has 3 partitions, then you should have 3 replicas
 
 If the connector crashes for some reason, or the Pod is scheduled to a different node, then Kubernetes will automatically restart it, and it'll pick up from the last message it processed.
 
-For retries, set the `asyncInvoke` option to `true`, so that consumed messages get put into the NATS JetStream queue and retried according to the policy you've defined. There are more advanced options covered in the docs and Helm chart, but what we've covered today should cover 80% of the use-cases for triggering functions from Kafka.
+For retries, set the `asyncInvocation` option to `true`, so that consumed messages get put into the NATS JetStream queue and retried according to the policy you've defined. There are more advanced options covered in the docs and Helm chart, but what we've covered today should cover 80% of the use-cases for triggering functions from Kafka.
 
 If you have any further questions, please feel [free to get in touch with us](https://www.openfaas.com/pricing).