diff --git a/layouts/default.html b/layouts/default.html
index 9713da1..0992453 100644
--- a/layouts/default.html
+++ b/layouts/default.html
@@ -96,6 +96,18 @@
       width: fit-content;
     }
 
+    .doll-quote figcaption {
+      font-size: 0.8em;
+      color: var(--dark2);
+      background-color: var(--middle1);
+      width: fit-content;
+      padding: 0 0.5ch;
+    }
+
+    .doll-quote figcaption + blockquote {
+      border-top: 2px solid var(--middle1);
+    }
+
     .mermaid {
       width: fit-content;
       color: var(--middle1);
diff --git a/log/002-soppy-wet-nix.doll b/log/002-soppy-wet-nix.doll
index 70832a2..3be7321 100644
--- a/log/002-soppy-wet-nix.doll
+++ b/log/002-soppy-wet-nix.doll
@@ -119,7 +119,7 @@ description: how it stores secrets alongside its code
 
 			age answers that question by letting doll use ed25519 keys to encrypt and decrypt doll's data.
 
-			[quote:ed25519 would be a good name for a doll... ^n]
+			[quote(important ^noe message):ed25519 would be a good name for a doll!!]
 
 			since we're deploying to machines with presumably an SSH server running, and presumably
 			the doll also has an SSH client, all of these ends have SSH keys we can use
@@ -366,7 +366,7 @@ description: how it stores secrets alongside its code
 	
 	&secrets........ but what about automation
 
-		that silly [code:.sops.yaml] thing huh, c:
+		that silly [code:.sops.yaml] third thing it mentioned huh? c:
 
 		why did we tag the age keys with [code:op_] and [code:m_]? so we can find them. in a script.