From 5cc52e66f4f2c279a75c248eeff904657e97fa17 Mon Sep 17 00:00:00 2001
From: Ayo <ramon.aycojr@gmail.com>
Date: Mon, 11 Dec 2023 20:20:40 +0100
Subject: [PATCH] feat(site): update why section

---
 site/src/pages/index.html | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/site/src/pages/index.html b/site/src/pages/index.html
index 59573a1..597e4cd 100644
--- a/site/src/pages/index.html
+++ b/site/src/pages/index.html
@@ -88,15 +88,18 @@
       <section>
         <p>Why use this base class?</p>
         <p>
-          Writing Web Components from the vanilla
+          Writing Web Components directly from
           <code-block inline>HTMLElement</code-block> can seem confusing and
           hard to maintain, especially when coming from popular JS frameworks.
         </p>
         <p>
-          This project aims to ease this with virtually zero tooling required
-          and working closest to vanilla custom element APIs. It works on
-          current-day browsers without needing compilers, transpilers, or
-          polyfills.
+          This project aims to address this with virtually zero tooling required
+          and thin abstractions from vanilla custom element APIs – giving you
+          only the bare minimum code to be productive.
+        </p>
+        <p>
+          It works on current-day browsers without needing compilers,
+          transpilers, or polyfills.
         </p>
         <p>
           Here's an interactive custom element: