Apply suggestions from code review

Co-authored-by: Meg McRoberts <[email protected]>
Signed-off-by: Florian Bacher <[email protected]>

docs/blog/posts/multi-stage-delivery-using-gitops.md

@@ -13,16 +13,16 @@ comments: true
 
 In multi-stage environments it can often become a challenge to keep an overview of
 how a particular version of a workload progresses through different stages.
-This can make it difficult to trace back which exact introduced a problem
+This can make it difficult to precisely trace exactly which modification introduced a problem
 when something goes wrong in one of the deployment stages.
 
 Having a distributed OpenTelemetry trace that encompasses all
 deployment stages and contains all relevant information,
 such as the git commit ID that triggered the deployment of a workload,
 helps to address this challenge.
 For example, if the evaluation of a load test in one of the deployment stages
-is failing, the distributed trace generated by Keptn not only contains
-details about the result of the evaluation, but also a link to the
+is failing, the distributed trace generated by Keptn contains
+details about the result of the evaluation, as well as a link to the
 deployment trace of the previous stage.
 This makes it easy to trace back the deployment of that particular workload
 across the previous stages, right until the original commit that resulted in
@@ -40,7 +40,8 @@ of a new workload version.
 
 For this, we are using the following technologies:
 
-- The new [KeptnAppContext CRD](../../docs/reference/crd-reference/appcontext.md)
+- The new [KeptnAppContext](../../docs/reference/crd-reference/appcontext.md)
+resource
   that allows to pass metadata to the generated deployment traces, and define a `promotion`
   task that is executed once the application is deployed and all post deployment checks have been
   executed successfully.