@@ -15,11 +15,11 @@ envision a place where developers have complete ownership of their code,
 open source communities can freely self-govern and most importantly,
 coding can be social and fun again.
 
-There are several models for decentralized social networks, ranging from
-ActivityPub's federated model, to Radicle's entirely P2P model. Our
-approach attempts to be the best of both worlds by adopting atproto -- a
-protocol for building decentralized social applications with a central
-identity.
+There are several models for decentralized code collaboration platforms,
+ranging from ActivityPub's (Forgejo) federated model, to Radicle's
+entirely P2P model. Our approach attempts to be the best of both worlds
+by adopting atproto -- a protocol for building decentralized social
+applications with a central identity.
 
 ![tangled architecture](/static/img/arch.svg)
 
@@ -34,9 +34,9 @@ consolidated "view" into the whole network, allowing users to access,
 clone and contribute to repositories hosted across different knots --
 completely seamlessly.
 
-Tangled is still in its infancy, and we're still building out several of
-its core features as we dogfood it ourselves. We developed these three
-core tenets to guide our decisions:
+Tangled is still in its infancy, and we're building out several of its
+core features as we dogfood it ourselves. We developed these three core
+tenets to guide our decisions:
 
 1. Ownership of data
 2. Low barrier to entry
@@ -44,7 +44,7 @@ 3. No compromise on user-experience
 
 Collaborating on code isn't easy, and the tools and workflows we use
 should feel natural and stay out of the way. Tangled's architecture
-enables common workflows to work as you'd expect, while remaining
+enables common workflows to work as you'd expect, all while remaining
 decentralized. 
 
 We believe that atproto has greatly simplfied one of the hardest parts