diff --git a/content/ecosystem/build-vs-buy/build-it-yourself/argo-cd.md b/content/ecosystem/build-vs-buy/build-it-yourself/argo-cd.md
index fc1d5a8..fde0e1c 100644
--- a/content/ecosystem/build-vs-buy/build-it-yourself/argo-cd.md
+++ b/content/ecosystem/build-vs-buy/build-it-yourself/argo-cd.md
@@ -8,7 +8,7 @@ url="/diy/argo-cd"
 **Claim:** Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes.
 
 
-**Focus:** Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. It follows the GitOps pattern of using Git repositories as the source of truth. You can define Kubernetes manifests in several different ways.
+**Focus:** Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. It follows the GitOps pattern of using Git repositories as the source of truth. Engineers love Argo CD for its great developer experience, especially in smaller organisations. But setting it up requires extensive experience in Kubernetes and DevOps tooling. In bigger and more complex setups, Argo CD is hard to scale, difficult to debug and requires constant maintenance.
 
 Website & docs: https://argo-cd.readthedocs.io/en/stable/
 
diff --git a/content/ecosystem/build-vs-buy/build-it-yourself/kubevela.md b/content/ecosystem/build-vs-buy/build-it-yourself/kubevela.md
index 499eb47..c68112c 100644
--- a/content/ecosystem/build-vs-buy/build-it-yourself/kubevela.md
+++ b/content/ecosystem/build-vs-buy/build-it-yourself/kubevela.md
@@ -7,7 +7,8 @@ url="/diy/kubevela"
 
 **Claim:** Make shipping applications more enjoyable.
 
-**Focus:** KubeVela introduced the open application model - programmatically describing the state of an application by encompassing the application configuration and the infrastructure configuration in a higher-level API. This approach keeps the environment specific elements of configurations (for example specific dependencies and resources) separated from the environment agnostic elements (such as the general architecture of workloads). Shifting to the open application model makes it necessary to restructure the entire config setup. Kubevela can be used as one of many components to orchestrate deployments.
+**Focus:** KubeVela introduced the open application model - programmatically describing the state of an application by encompassing the application configuration and the infrastructure configuration in a higher-level API. This approach keeps the environment specific elements of configurations (for example specific dependencies and resources) separated from the environment agnostic elements (such as the general architecture of workloads).Kubevela can be used as one of many components to orchestrate deployments. 
+Shifting to the open application model makes it necessary to restructure the entire config setup.
 
 Website: https://kubevela.io/
 
diff --git a/content/ecosystem/build-vs-buy/frameworks/upbound.md b/content/ecosystem/build-vs-buy/frameworks/upbound.md
index ddd44db..204ab18 100644
--- a/content/ecosystem/build-vs-buy/frameworks/upbound.md
+++ b/content/ecosystem/build-vs-buy/frameworks/upbound.md
@@ -7,7 +7,7 @@ url="/frameworks/upbound"
 
 **Claim:** Universal cloud APIs and consoles for your team
 
-**Focus:** Upbound helps teams build artificial cloud providers that developers can operate themselves. 
+**Focus:** Upbound offers a UI layer to manage several Crossplane modules. Upbound itself deals only with infrastructure orchestration. The dynamic composition of configurations or automated workflows are not covered by the product. Upbound only works for developers who want to unify everything against Crossplane, a task that usually isn’t feasible if you have for example already existing IaC modules in place. Some developers may find the system redundant if they’re building a platform and have to build a more overarching UI layer. 
 
 **Website:** [upbound.io](https://upbound.io/)