Update blog/docs/articles/aws_to_func_migration.md

Co-authored-by: Luke Kingland <luke@lukekingland.com>
knative · knative-prow · Jun 24, 2024 · Jun 17, 2024 · Jun 18, 2024 · Jun 24, 2024
commit 5e8441b362ec1d0bb28777868fb9d46777dccabf
diff --git 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.
Original file line number	Diff line number	Diff line change
		@@ -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.