diff --git a/lens/private/scribblings/guide/built-in/ordered.scrbl b/lens/private/scribblings/guide/built-in/ordered.scrbl
index a83a14a..bb59452 100644
--- a/lens/private/scribblings/guide/built-in/ordered.scrbl
+++ b/lens/private/scribblings/guide/built-in/ordered.scrbl
@@ -14,7 +14,7 @@
 Many Racket data structures hold @emph{ordered} or @emph{sequential} values. Lenses for accessing
 elements of these structures by index are provided.
 
-@section[#:tag "pair-list-guide"]{Pairs and Lists}
+@section[#:tag "pair-list-guide" #:style 'quiet]{Pairs and Lists}
 
 @see-reference-note["pair-list-reference"]{pair and list lenses}
 
diff --git a/lens/private/scribblings/guide/introduction.scrbl b/lens/private/scribblings/guide/introduction.scrbl
index f1f99e5..59e1ce3 100644
--- a/lens/private/scribblings/guide/introduction.scrbl
+++ b/lens/private/scribblings/guide/introduction.scrbl
@@ -72,7 +72,7 @@ update the “view” based on its existing value. For example, we could increme
 @(interaction #:eval introduction-eval
   (lens-transform cdr-lens (cons 1 2) add1))
 
-@section{Why use lenses?}
+@section[#:style 'quiet]{Why use lenses?}
 
 So far, lenses just seem like a way to group getters and setters, and as we've seen, that's all they
 really are. However, on their own, this wouldn't be very useful. Using @racket[(car _p)] is a lot