diff --git a/docs/backends.rst b/docs/backends.rst
index 2909b5a..9c99f3f 100644
--- a/docs/backends.rst
+++ b/docs/backends.rst
@@ -1,5 +1,5 @@
-Backends: Vector vs. Raster
-===========================
+Vector vs. Raster Backends
+==========================
 
 Squib's graphics rendering engine, Cairo, has the ability to support a variety of surfaces to draw on, including both raster images stored in memory and vectors stored in SVG files. Thus, Squib supports the ability to handle both. They are options in the configuration file ``backend: memory`` or ``backend: svg`` described in :doc:`/config`.
 
diff --git a/docs/bleed.rst b/docs/bleed.rst
index 241da5e..976aa1a 100644
--- a/docs/bleed.rst
+++ b/docs/bleed.rst
@@ -1,4 +1,13 @@
-Handling Printing Bleeds
-========================
+Always Have Bleed
+=================
 
-TODO: Write this.
+.. note::
+
+  TODO: Under construction
+
+* Always plan to have a printing bleed around the edge of your cards. 1/8 in is standard
+* Have a safe zone too
+* Layouts make this easy (see the built-in layouts)
+* Can use png overlays from templates to make sure it fits
+* Trim option is what is used everywhere in Squib
+* Trim_radius also lets you show your cards off like how they'll really look
diff --git a/docs/build_groups.rst b/docs/build_groups.rst
index 5f06b19..9eb886f 100644
--- a/docs/build_groups.rst
+++ b/docs/build_groups.rst
@@ -1,5 +1,5 @@
-Use Groups for Custom Builds
-============================
+Group Your Builds
+=================
 
 Often in the prototyping process you'll find yourself cycling between running your overall build and building a single card. You'll probably be commenting out code in the process.
 
diff --git a/docs/index.rst b/docs/index.rst
index 8082068..ac07784 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -1,4 +1,3 @@
-
 Squib Documentation
 ===================