diff --git a/docs/content/014-guides/020-schema.mdx b/docs/content/014-guides/020-schema.mdx
index 9f8a033e..0e86e4bd 100644
--- a/docs/content/014-guides/020-schema.mdx
+++ b/docs/content/014-guides/020-schema.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Schema'
+title: Schema
 tocDepth: 2
 ---
 
diff --git a/docs/content/014-guides/021-nullability.mdx b/docs/content/014-guides/021-nullability.mdx
index 92dd85ed..67c82f0e 100644
--- a/docs/content/014-guides/021-nullability.mdx
+++ b/docs/content/014-guides/021-nullability.mdx
@@ -1,3 +1,8 @@
+---
+title: Nullability
+tocDepth: 2
+---
+
 ## Nullability in principle
 
 When creating an API, especially before going to production or lifting features out of beta, thinking about if arguments and input object fields (_inputs_) should be required and if object type fields (_outputs_) should be nullable is an important design consideration. How easy your API is to consume trades for how easy it is to change and some reliability characteristics.