diff --git a/docs/tour/why-wasmcloud.mdx b/docs/tour/why-wasmcloud.mdx
index 17deecd6..608aeb1f 100644
--- a/docs/tour/why-wasmcloud.mdx
+++ b/docs/tour/why-wasmcloud.mdx
@@ -83,7 +83,7 @@ Logs from hosts running in Docker, if started with our docker compose, can be fo
 
 # Hello Universe
 
-You've now built a simple microservice with wasmCloud that uses common capabilities (handle HTTP requests, interface with a key-value store) that many cloud native applications need. So, _why wasmCloud_? What makes this application that you built different from similar apps on other platforms? Beyond providing an easy-to-use platform that's quick to get started with, we also want to make sure that you understand that the biggest benefits of wasmCloud come after you've built your application.
+You've now built a simple microservice with wasmCloud that uses common capabilities (handle HTTP requests, interface with a key-value store) that many cloud native applications need. So, _why wasmCloud_? What makes this application that you built different from similar apps on other platforms? wasmCloud is an easy-to-use platform that's quick to get started with, which is essential for a great and intuitive developer experience, and this project extends far beyond "Hello World." This page emphasizes the intention behind the design of wasmCloud, and the benefits that follow after you've built your application.
 
 Now that your microservice is running, consider what you may have to do to actually deploy that to production in the cloud. If you're building this application in a modern language and packaging it up into a container, you may have the following hurdles to consider _before you even get to the point of writing your features in the first place_: