From a0e400aaffab8844d097e41b4ba6b94ead946d04 Mon Sep 17 00:00:00 2001
From: Jim Salter <github@jrs-s.net>
Date: Mon, 4 Jul 2016 16:34:06 -0400
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index eb9f563..d0b3378 100644
--- a/README.md
+++ b/README.md
@@ -3,8 +3,8 @@
 
 <img src="http://openoid.net/gplv3-127x51.png" width=127 height=51 align="right">Sanoid is a policy-driven snapshot management tool for ZFS filesystems.  When combined with the Linux KVM hypervisor, you can use it to make your systems <a href="http://openoid.net/transcend" target="_blank">functionally immortal</a>.  
 
-[![Sanoid rollback demo](http://www.openoid.net/sanoid_video_launcher.png)](https://youtu.be/ZgowLNBsu00 "Sanoid rollback demo")
-(Real time demo: rolling back a full-scale cryptomalware infection in seconds)
+<p align="center"><a href="https://youtu.be/ZgowLNBsu00" target="_blank"><img src="http://www.openoid.net/sanoid_video_launcher.png"></a>
+(Real time demo: rolling back a full-scale cryptomalware infection in seconds!)</p>
 
 More prosaically, you can use Sanoid to create, automatically thin, and monitor snapshots and pool health from a single eminently human-readable TOML config file at /etc/sanoid/sanoid.conf.  (Sanoid also requires a "defaults" file located at /etc/sanoid/sanoid.defaults.conf, which is not user-editable.)  A typical Sanoid system would have a single cron job: