testing.textile in assaf-buildr-1.3.4

- old
+ new
@@ -193,10 +193,10 @@
 |_. Method |_. Checks that ... |
 | @exist@   | Given a file task checks that the file (or directory) exists. |
 | @empty@   | Given a file task checks that the file (or directory) is empty. |
 | @contain@ | Given a file task referencing a file, checks its contents, using string or regular expression.  For a file task referencing a directory, checks that it contains the specified files; global patterns using @*@ and @**@ are allowed. |
 
-All these matchers operate against a file task.  If you run them against a ZipTask (including JAR, WAR, etc) they can also check the contents of the ZIP file.  And as you can see in the examples above, you can also run them against a path in a ZIP file, checking its contents as if it was a directory, or against an entry in a ZIP file, checking the content of that file.
+All these matchers operate against a file task.  If you run them against a ZipTask (including JAR, WAR, etc) or a TarTask, they can also check the contents of the archive.  And as you can see in the examples above, you can also run them against a path in an archive, checking its contents as if it was a directory, or against an entry in an archive, checking the content of that file.
 
 p(note). The @package@ method returns a package task based on packaging type, identifier, group, version and classifier.  The last four are inferred, but if you create a package with different specifications (for example, you specify a classifier) your checks must call @package@ with the same qualifying arguments to return the very same package task.
 
 Buildr expectations are based on RSpec.  "RSpec":http://rspec.info/ is the behavior-driven development framework we use to test Buildr itself.  Check the RSpec documentation if want to see all the supported matchers, or want to write your own.
 