diff --git a/assets/sass/main.scss b/assets/sass/main.scss
index d7e3a03..b1626e9 100644
--- a/assets/sass/main.scss
+++ b/assets/sass/main.scss
@@ -39,7 +39,7 @@ li {
   word-break: break-word;
   overflow-wrap: break-word;
   font-weight: 200;
-  line-height: 1.6;
+  line-height: 1.56;
   letter-spacing: 0.02em;
   word-spacing: 0.05em;
   margin-top: 0;
@@ -68,12 +68,12 @@ h1 {
   padding-bottom: 0.5rem;
   font-size: 2.5rem;
   @media print, (max-width: 600px) {
-    font-size: 1.8rem;
+    font-size: 1.9rem;
   }
   margin-top: 0;
 }
 h2 {
-  font-size: 1.8rem;
+  font-size: 1.9rem;
   @media print, (max-width: 600px) {
     font-size: 1.3rem;
   }
@@ -134,7 +134,7 @@ em {
 strong {
   font-variant: small-caps;
   letter-spacing: 0.05em;
-  font-weight: 800;
+  font-weight: 600;
 }
 
 ul {
diff --git a/content/posts/2023-shape-up-cadences/index.md b/content/posts/2023-shape-up-cadences/index.md
index f48587b..4d7802c 100644
--- a/content/posts/2023-shape-up-cadences/index.md
+++ b/content/posts/2023-shape-up-cadences/index.md
@@ -1,7 +1,6 @@
 ---
 title: "Innovating Product Process Cadence: Shape Up Beyond 6+2"
-date: 2023-10-27
-draft: true
+date: 2023-11-10
 
 image: "2023-10-27-shape-up-cadences.png"
 ---
@@ -13,37 +12,49 @@ While I am currently bootstrapping a startup idea centered on Shape Up tooling,
 ## Classic (6+2)
 
 **Method**: 6 weeks of building, followed by 2 weeks of cooldown.
+
 **Cooldown**: 2 weeks
+
 **Best For**: The staple for many, including Basecamp. Ideal for teams looking for a time-tested approach.
 
 ## Collective Shaping (6+?)
 
 **Method**: Shaping until consensus, then a 6-week building cycle.
+
 **Cooldown**: To be decided (indicated by "?")
+
 **Best For**: Teams valuing collective decision-making with a flexible cooldown. On-call rotations or enablement teams are sometimes used here.
 
 ## The Dynamic (X)
 
 **Method**: Entirely flexible cycle length, often with just one developer per project.
+
 **Cooldown**: No fixed period
+
 **Best For**: Small, agile teams where adaptability is key.
 
 ## The Deliberate (4+1+1)
 
 **Method**: 4 weeks of building, followed by 1 week for framing adjustments, and another week for final solution shaping before starting with the building cycle.
+
 **Cooldown**: 2 weeks segmented into framing and solution shaping
+
 **Best For**: Teams needing precise planning and coordinated availability during cooldown.
 
 ## The Quarter-Match (5+2)
 
 **Method**: 5 weeks of tech-only building to fit into fiscal quarters, followed by 2 weeks of cooldown.
+
 **Cooldown**: 2 weeks
+
 **Best For**: Corporate teams guided by fiscal calendars.
 
 ## The Comprehensive (6+2+2)
 
 **Method**: 6 weeks of building, 2 weeks for release and polishing, followed by 2 weeks of cooldown.
+
 **Cooldown**: 4 weeks (2 for release and polishing, 2 for cooldown)
+
 **Best For**: Larger, mature teams desiring a comprehensive cycle, including a release phase.
 
 ## Conclusion