From 5e8441b362ec1d0bb28777868fb9d46777dccabf Mon Sep 17 00:00:00 2001 From: Matthias Wessendorf Date: Mon, 24 Jun 2024 11:28:25 +0200 Subject: [PATCH] Update blog/docs/articles/aws_to_func_migration.md Co-authored-by: Luke Kingland --- blog/docs/articles/aws_to_func_migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/docs/articles/aws_to_func_migration.md b/blog/docs/articles/aws_to_func_migration.md index 7685640c130..f108c7e2d52 100644 --- a/blog/docs/articles/aws_to_func_migration.md +++ b/blog/docs/articles/aws_to_func_migration.md @@ -102,4 +102,4 @@ $ curl -v -X POST \ ## Conclusion -With Knative Functions it is pretty straightforward to build cloud vendor-neutral function for consuming event notifications from 3rd party cloud services, such as AWS S3. Deploying those functions as Linux containers to your own on-premise Kubernetes cluster is supported by the Knative CLI as well as testing the function locally. +With Knative Functions it is straightforward to build cloud vendor-neutral functions for consuming event notifications from 3rd party cloud services such as AWS S3. Deploying those functions as Linux containers to your own on-premise Kubernetes cluster is also supported by the Knative CLI, as well as testing the function locally.