diff --git a/content/backing-services.md b/content/backing-services.md
index 3c2482a..934e9fb 100644
--- a/content/backing-services.md
+++ b/content/backing-services.md
@@ -9,7 +9,7 @@ Backing services like the database are traditionally managed by the same systems
 
 Each distinct backing service is a *resource*.  For example, a MySQL database is a resource; two MySQL databases (used for sharding at the application layer) qualify as two distinct resources.  The twelve-factor app treats these databases as *attached resources*, which indicates their loose coupling to the deploy they are attached to.
 
-<img src="/images/attached-resources.png" style="float: none" alt="A production deploy attached to four backing services." />
+<img src="/images/attached-resources.png" class="full" alt="A production deploy attached to four backing services." />
 
 Resources can be attached and detached to deploys at will.  For example, if the app's database is misbeaving due to a hardware issue, the app's administrator might spin up a new database server restored from a recent backup.  The current production database could be detached, and the new database attached -- all without any code changes.
 
diff --git a/public/style.css b/public/style.css
index f5e2ea2..6ea53d8 100644
--- a/public/style.css
+++ b/public/style.css
@@ -31,7 +31,7 @@ header a {
 section {
   padding-top: 16pt;
   text-align: center;
-  min-width: 70em;
+  min-width: 65em;
 }
 section h1 {
   font-size: 19pt;
@@ -43,7 +43,7 @@ article {
 article, nav {
   margin: 0 auto;
   text-align: justify;
-  width: 60em;
+  width: 55em;
 }
 article p a, article li a {
   text-decoration: none;
@@ -136,3 +136,8 @@ article img {
   float: right;
   margin-left: 32pt;
 }
+
+article img.full {
+  float: none;
+  margin-left: 0;
+}