From cd0caa9696e5626717bba0eeeb0a384e05e68406 Mon Sep 17 00:00:00 2001 From: Danielle Date: Tue, 12 Mar 2024 19:12:00 +0100 Subject: [PATCH] Update index.md Co-authored-by: MacKenzie Olson Signed-off-by: Danielle --- content/en/blog/news/first-post/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/news/first-post/index.md b/content/en/blog/news/first-post/index.md index a7c71a8..f667ac6 100644 --- a/content/en/blog/news/first-post/index.md +++ b/content/en/blog/news/first-post/index.md @@ -51,7 +51,7 @@ To illustrate this point, below are all the steps required to start a Kubernetes | Pod ready | The Pod responds to the asynchronous readiness probe and signals that it is now ready | | Service ready | The Pod gets added to the list of active endpoints for a Service and can start receiving traffic | -This process, and the amount of duplication that occurs on every replica, even if they are running on the same physical hardware, is where the [Spin][spin] WebAssembly Runtime and SpinKube shines. +Circumventing this process, and the amount of duplication that occurs on every replica even if they are running on the same physical hardware, is where the [Spin][spin] WebAssembly Runtime and SpinKube shines. ## Why SpinKube?