chore: edits

diff --git a/src/demo/about.md b/src/demo/about.md
index 6058c714d4dc6b014595e6f99c2a98e6ee5b1e50..b4d0c130fb2342f35f889603871d187014ade324 100644 (file)
--- a/src/demo/about.md
+++ b/src/demo/about.md
@@ -7,8 +7,8 @@ last_updated: 20241123084949
 
 [Pandoc](https://pandoc.org/) deserves to be mentioned before Jetsam as it's the 
 real workhorse of this operation. Jetsam can be described as a Pandoc-based 
-distribution of writing utilities designed to help you write, publish, and 
-maintain a corpus of personal-space writings.
+distribution of writing utilities that are designed to help you write, publish, 
+and maintain a corpus of personal-space writings.
 
 # About Personal-Space Writing and Jetsam Philosophy
 
@@ -23,13 +23,12 @@ The following principles of personal-space writing help govern the philosophy of
 choose something that won't lock you in. Either the format should be relevant 
 in 20 years or you should be able to be easily port it to whatever is relevant in 
 20 years. 
-* **Next, prioritize predicably stable tools.** Even if you choose a simple data 
+* **Next, prioritize predicable, stable tools.** Even if you choose a simple data 
 format, each application tends to have its own quirks about how it handles the 
 data. When you accumulate a volume of data, migrating becomes non-trivial even 
 for small deviations. Each new dependency incurs a maintenance cost, so it deserves 
 scrutiny. When you add a new dependency, try to 
-[Choose Boring Technology](https://mcfunley.com/choose-boring-technology) as the 
-maintenance risk of _<boring project\>_ tends to be much lower than _<the new hotness\>_.
+[Choose Boring Technology](https://mcfunley.com/choose-boring-technology) because the maintenance risk of _<boring project\>_ tends to be much lower than _<the new hotness\>_.
 * **Then, prioritize extensibility.** Ostensibly, a personalized space is the 
 goal. So, why is it last in this list of priorities? Because, if you don't 
 have the stability offered by the previous priorities, you'll spend an awful 
@@ -39,8 +38,8 @@ boring technology.
 With those guidelines in mind, you can see why we rely so heavily on Pandoc.
 
 * **We can use Markdown as our primary data format.** Markdown is a simple 
-standard, which makes it easy to create tools for. Furthermore, it's a text-
-based standard, so if all else fails, it's still readable.
+standard, which makes it easy to create tools for. Furthermore, it's a 
+text-based standard, so if all else fails, it's still readable.
 * **Pandoc is its own data migration tool.** This includes migrating between 
 different flavors of Markdown.
 * **Pandoc is relatively stable with ongoing support.** There have been 3 major