Update index.md

Co-authored-by: MacKenzie Olson <mackenzie.olson@fermyon.com>
Signed-off-by: Danielle <dani@builds.terrible.systems>

content/en/blog/news/first-post/index.md

@@ -38,7 +38,7 @@ The desire to fix many of these issues is what led to the "first" generation of
 
 First generation serverless runtimes (such as AWS Lambda, Google Cloud Functions, Azure Functions, and their Kubernetes counterparts OpenWhisk and KNative) are all based on the principle of running a VM or container per function. While this afforded flexibility for application developers, complexity was introduced to platform engineers as neither compute type is designed to start quickly. Platform engineers operating these serverless platforms became responsible for an elaborate dance of pre-warming compute capacity and loading a workload just-in-time, making for a difficult tradeoff in cold start performance and cost. The result? A slow and inefficient first generation of Serverless.
 
-See the following that describes the process of starting a Kubernetes Pod:
+To illustrate this point, below are all the steps required to start a Kubernetes Pod:
 
 | Phase | Description |
 | --- | --- |