add strings

state_of_html.yml

@@ -185,7 +185,7 @@ translations:
     t: Interactivity Pain Points
   - key: features.interactivity_pain_points.question
     t: What are your pain points around dynamic HTML changes?
-  - key: features.interactivity_pain_points.description
+  - key: features.interactivity_pain_points.prompt
     t: |
       Browser incompatibilities or lack of support, missing features, and other problems you face
       around interactive elements and behaviors (except forms), DOM manipulation, events, and related APIs.
@@ -270,7 +270,7 @@ translations:
     t: Content Pain Points
   - key: features.content_pain_points.question
     t: What are your pain points around managing content in HTML?
-  - key: features.content_pain_points.description
+  - key: features.content_pain_points.prompt
     t: |
       Think of embedding (multimedia, iframes, SVG, etc), machine-readable data, internationalization & localization, security & privacy, performance etc.
       Missing features, browser incompatibilities, and other problems you face are all fair game.
@@ -337,7 +337,7 @@ translations:
     t: Using Web Components Pain Points
   - key: features.using_web_components_pain_points.question
     t: What are your biggest pain points around *consuming* web components?
-  - key: features.using_web_components_pain_points.description
+  - key: features.using_web_components_pain_points.prompt
     t: Using Web Components that you or others have made. Missing features, browser incompatibilities, etc.
   - key: features.using_web_components_pain_points.placeholder
     t: |
@@ -347,7 +347,7 @@ translations:
     t: Making Web Components Pain Points
   - key: features.making_web_components_pain_points.question
     t: What are your biggest pain points around *making* web components?
-  - key: features.making_web_components_pain_points.description
+  - key: features.making_web_components_pain_points.prompt
     t: |
       What prevents you from creating the amazing components you envision? Missing features, browser incompatibilities, etc.
   - key: features.making_web_components_pain_points.placeholder

state_of_html_2023.yml

@@ -28,6 +28,9 @@ translations:
       insights in the process, be sure to let us know!
 
 
+      You can learn more about all this in [this post](https://dev.to/sachagreif/discover-the-state-of-html-2023-survey-results-n10), or by watching a [quick YouTube video](https://www.youtube.com/watch?v=G-rFwp2zUT4)
+
+
       With all this out of the day, welcome to the results for the first ever State of HTML survey. 
       After this, I'm willing to bet you won't look at good old HTML quite the same way ever again!
 
@@ -87,7 +90,10 @@ translations:
 
   - key: features.all_features.description
     t: |
-      This chart recaps all of the survey's feature questions. You can also find a more specific breakdown of the same data in each feature sub-section.
+      This chart recaps all of the survey's feature questions. The main bars represent a respondent's experience; and they are then further subdivided according to that respondent's sentiment. You can change the grouping to alternate between both. 
+
+
+      Note that you can also find a more specific breakdown of the same data in each feature sub-section.
 
   ###########################################################################
   # Sponsors
@@ -107,19 +113,7 @@ translations:
   ###########################################################################
 
   - key: conclusion.html2023.bio
-    t: Lead Maintainer, State of HTML Survey
+    t: W3C Technical Architecture Group Member & MIT CSAIL Researcher
   - key: conclusion.html2023
     t: >
-      HTML has gone through a real hero's journey over its existence. Born as a humble document description language, it soon evolved into something much more powerful, receiving its own content styling features and interaction capabilities. 
-
-
-      But as the web grew, CSS and JavaScript came out from HTML's shadow and both grew much more powerful than poor HTML could ever dream of, and relegated it to a secondary role. 
-
-
-      Yet over the years, web developers have grown disillusioned with having to reimplement the same basic components over and over again. While some have put their faith in JavaScript frameworks, and other wait for the promised Web Components Era, others yet are wondering if maybe the solution wasn't under our eyes all along. Could it be HTML's time to shine again?
-
-
-      Browser vendors certainly seem to think so, with many new elements and APIs having been introduced over the last couple years – and many more yet to come. 
-
-
-      And while this initial State of HTML has been quite instructive, I personally can't wait to see how the data evolves. So I hope you'll join us next year (or rather, this year!) as well, and come along HTML's next adventure!
+      Coming soon…