diff --git a/docs/index.html b/docs/index.html
index 4c83cf70..c497a2ef 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -31,7 +31,7 @@
-
+
diff --git a/docs/ja-JP/index.html b/docs/ja-JP/index.html
index c356c7aa..9ba353e9 100644
--- a/docs/ja-JP/index.html
+++ b/docs/ja-JP/index.html
@@ -32,7 +32,7 @@
-
+
diff --git a/docs/news/2020-09-20.html b/docs/news/2020-09-20.html
index 42fc213c..1dab6115 100644
--- a/docs/news/2020-09-20.html
+++ b/docs/news/2020-09-20.html
@@ -26,7 +26,7 @@
-
+
@@ -101,9 +101,11 @@
a normal web page.
- The new tech stack is, frankly, pretty amazing. It does some thing that weren't possible even a year ago, let alone back in 2016, and this is
- the first in a series of posts on how the new tech stack works. To give a bit of a teaser, the series will cover:
+ The new tech stack is, frankly, pretty amazing. It does some things that weren't possible even half a year before I started the rewrite, let
+ alone being possible in 2016, and so because so much has changed, this post will be the first in a series of posts on how the new tech stack
+ works.
+ To give a bit of a teaser, some of the things I'll be writing about:
- Essentially reinventing (a limited form of) Processing.js
- Writing a custom build system, because I'm exhausted with Webpack and hope to never use it again.
diff --git a/docs/news/2020-09-20.md b/docs/news/2020-09-20.md
index 4d48c5cb..1619027e 100644
--- a/docs/news/2020-09-20.md
+++ b/docs/news/2020-09-20.md
@@ -6,7 +6,9 @@ So, in 2016, when [React.js]() exploded onto the scene, I rewrote the primer as
So I left it a regular React app, and every time I thought "wouldn't it be nice if it was just... a web page again?" the browser landscape just hadn't caught up. Finally, in 2020, things are different: with a global pandemic, and some vacation time, and something random causing me to look up the state of HTML custom elements, everything was pointing at it being time to finally, _finally_, turn the Primer back into a normal web page.
-The new tech stack is, frankly, pretty amazing. It does some thing that weren't possible even a year ago, let alone back in 2016, and this is the first in a series of posts on how the new tech stack works. To give a bit of a teaser, the series will cover:
+The new tech stack is, frankly, pretty amazing. It does some things that weren't possible even half a year before I started the rewrite, let alone being possible in 2016, and so because so much has changed, this post will be the first in a series of posts on how the new tech stack works.
+
+To give a bit of a teaser, some of the things I'll be writing about:
- Essentially reinventing (a limited form of) Processing.js
- Writing a custom build system, because I'm exhausted with Webpack and hope to never use it again.
diff --git a/docs/news/rss.xml b/docs/news/rss.xml
index c7a3b3e4..00c70690 100644
--- a/docs/news/rss.xml
+++ b/docs/news/rss.xml
@@ -21,7 +21,8 @@
<p>Once upon a time, I needed to draw some Bezier curves because I was trying to create a Japanese kanji composition system that turned strokes into outlines, and that required knowing how to offset Bezier curves and... at the time (2011, time flies) there was no good single source of information for Bezier curves on the web. So I made one. Sure it started small, but it turns out that if you just keep adding bits to something, several years later you have quite the monster, and a single HTML file becomes intractible.</p>
<p>So, in 2016, when <a href="">React.js</a> exploded onto the scene, I rewrote the primer as a React app, and it became a lot easier to maintain. Like, <em>a lot</em> a lot. However, there was a downside: no JS meant no content. Sure, server-side rendering sort of existed, but not really, and because the Primer is hosted through github, there was no "server" to run. Plus, trying to rehydrate an app the size of the Primer from a giant HTML file had truly <em>dire</em> performance.</p>
<p>So I left it a regular React app, and every time I thought "wouldn't it be nice if it was just... a web page again?" the browser landscape just hadn't caught up. Finally, in 2020, things are different: with a global pandemic, and some vacation time, and something random causing me to look up the state of HTML custom elements, everything was pointing at it being time to finally, <em>finally</em>, turn the Primer back into a normal web page.</p>
-<p>The new tech stack is, frankly, pretty amazing. It does some thing that weren't possible even a year ago, let alone back in 2016, and this is the first in a series of posts on how the new tech stack works. To give a bit of a teaser, the series will cover:</p>
+<p>The new tech stack is, frankly, pretty amazing. It does some things that weren't possible even half a year before I started the rewrite, let alone being possible in 2016, and so because so much has changed, this post will be the first in a series of posts on how the new tech stack works.</p>
+<p>To give a bit of a teaser, some of the things I'll be writing about:</p>
<ul>
<li>Essentially reinventing (a limited form of) Processing.js</li>
<li>Writing a custom build system, because I'm exhausted with Webpack and hope to never use it again.</li>
diff --git a/docs/zh-CN/index.html b/docs/zh-CN/index.html
index e0ad72e0..8ae08658 100644
--- a/docs/zh-CN/index.html
+++ b/docs/zh-CN/index.html
@@ -32,7 +32,7 @@
-
+