2ddd7cacb25e
Typo.
| author | Steve Losh <steve@stevelosh.com> |
|---|---|
| date | Tue, 06 Sep 2011 12:25:48 -0400 |
| parents | 63f34d8aff14 |
| children | de680e8629f9 |
| branches/tags | (none) |
| files | content/blog/2011/09/writing-vim-plugins.html |
Changes
--- 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?