Replace "spermy" with "approximate" to mirror the RubyGems change in …

…terminology

in pull request rubygems/rubygems#124

lib/cocoapods-core/vendor/version.rb

@@ -131,7 +131,7 @@ module Pod::Vendor
   # specify your dependency as ">= 2.0.0" then, you're good, right? What
   # happens if fnord 3.0 comes out and it isn't backwards compatible
   # with 2.y.z? Your stuff will break as a result of using ">=". The
-  # better route is to specify your dependency with a "spermy" version
+  # better route is to specify your dependency with a "approximate" version
   # specifier. They're a tad confusing, so here is how the dependency
   # specifiers work:
   #
@@ -288,7 +288,7 @@ def segments # :nodoc:
       ##
       # A recommended version for use with a ~> Requirement.
 
-      def spermy_recommendation
+      def approximate_recommendation
         segments = self.segments.dup
 
         segments.pop    while segments.any? { |s| String === s }