diff --git a/docs/themes/smithy/landing.html b/docs/themes/smithy/landing.html
index 80ce1c60651..f0add6af3a6 100644
--- a/docs/themes/smithy/landing.html
+++ b/docs/themes/smithy/landing.html
@@ -7,8 +7,8 @@
                     <h1>Smithy, an extensible API definition language</h1>
                     <div class="headline">
                         Smithy <span class="splash-highlight">defines</span> and
-                        <span class="splash-highlight">generates</span> services,
-                        clients, and documentation for any protocol.
+                        <span class="splash-highlight">generates</span> clients,
+                        services, and documentation for any protocol.
                     </div>
                     <a class="splash-link" href="quickstart.html">Get started</a>
                     <a class="splash-link-small" href="spec/index.html">Specifications</a>
@@ -42,30 +42,30 @@ <h1>Smithy, an extensible API definition language</h1>
     <div class="width-wrapper">
         <div class="splash-row">
             <div class="splash-column">
-                <h2>Protocol-agnostic</h2>
+                <h2>🤖 &nbsp;Protocol-agnostic</h2>
                 <p>Smithy is designed to work with any programming language, describe
-                    services running in any environment, and work with any kind of transport or
-                    serialization format.</p>
+                    services running in any environment, and work with any kind of
+                    transport or serialization format.</p>
             </div>
             <div class="splash-column">
-                <h2>Designed to evolve</h2>
-                <p>Smithy can be extended through <em>traits</em>. Smithy's extensible
-                   meta-model can capture more information about services and allows it to
-                   evolve without breaking changes.</p>
+                <h2>🧬 &nbsp;Designed to evolve</h2>
+                <p>Smithy is extended through <em>traits</em>. Smithy's extensible
+                   meta-model can evolve and capture more information about services
+                   without breaking changes.</p>
             </div>
         </div>
         <div class="splash-row">
             <div class="splash-column">
-                <h2>Codify and enforce API governance</h2>
-                <p>Customizable standards and validation constraints ensure that APIs
-                    adhere to any kind of standard or convention. Rules can be
-                    shared and applied to all APIs in an organization.</p>
+                <h2>⚖ &nbsp;Codify and enforce API governance</h2>
+                <p>Customizable API standards help to automatically ensure that APIs
+                    meet customer expectations. Validation rules can be shared and
+                    applied to all APIs in an organization.</p>
             </div>
             <div class="splash-column">
-                <h2>Resource based</h2>
-                <p>Smithy is defined in terms of resources and operations you can enact on
-                    them. Explicitly defining resources provides rich metadata about an API
-                    that can be used in model transformations.</p>
+                <h2>🖇️ &nbsp;Resource based</h2>
+                <p>Smithy models are defined by resources and operations. Defining
+                    services with resources helps lead to better APIs and provides
+                    rich information for model transformations.</p>
             </div>
         </div>
     </div>