From: Shawn M Moore <sartak@gmail.com>
Date: Sun, 12 Jul 2009 23:15:09 +0000 (-0400)
Subject: trade-off is more correct than tradeoff
X-Git-Tag: 0.88~20
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=dd8a021cdb26d65f7dbdb37273978d8da5ef9a24;p=gitmo%2FMoose.git

trade-off is more correct than tradeoff
---

diff --git a/lib/Moose/Manual/BestPractices.pod b/lib/Moose/Manual/BestPractices.pod
index 1db01de..3a8e104 100644
--- a/lib/Moose/Manual/BestPractices.pod
+++ b/lib/Moose/Manual/BestPractices.pod
@@ -36,7 +36,7 @@ The C<no Moose> bit is simply good code hygiene, as it removes all the
 Moose keywords from your class's namespace. Once the class has been
 built, these keywords are not needed needed. The C<make_immutable>
 call allows Moose to speed up a lot of things, most notably object
-construction. The tradeoff is that you can no longer change the class
+construction. The trade-off is that you can no longer change the class
 definition.
 
 A more generic way to unimport not only L<Moose>'s exports but also