# HG changeset patch
# User Steve Losh <steve@stevelosh.com>
# Date 1315326348 14400
# Node ID 2ddd7cacb25e7d9efd970e0dd1dfc64f64d0f3c1
# Parent  63f34d8aff1408eda654fa8ca3fc34b86fab6871
Typo.

diff -r 63f34d8aff14 -r 2ddd7cacb25e content/blog/2011/09/writing-vim-plugins.html
--- a/content/blog/2011/09/writing-vim-plugins.html	Tue Sep 06 09:12:16 2011 -0400
+++ b/content/blog/2011/09/writing-vim-plugins.html	Tue Sep 06 12:25:48 2011 -0400
@@ -297,7 +297,7 @@
 day and burn into their muscle memory.  Users rely on tools to work, and tools that
 break backwards compatibility will quickly lose users' trust.
 
-Maintaining backwards comaptibility will cause your plugin's code to get crufty in
+Maintaining backwards compatibility will cause your plugin's code to get crufty in
 spots, but it's the price of maintaining your users' happiness.
 
 ### What Matters for Backards Compatibility?