remove introductory paragraph that described other tools unrelated to…

… `flate2`

src/gz/bufread.rs

@@ -172,8 +172,8 @@ impl<R: BufRead + Write> Write for GzEncoder<R> {
 /// This structure exposes a [`BufRead`] interface, reading compressed data
 /// from the underlying reader, and emitting uncompressed data.
 ///
-/// After reading a single member of the gzip data this reader will return 
-/// Ok(0) even if there are more bytes available in the underlying reader. 
+/// After reading a single member of the gzip data this reader will return
+/// Ok(0) even if there are more bytes available in the underlying reader.
 /// If you need the following bytes, call `into_inner()` after Ok(0) to
 /// recover the underlying reader.
 ///

src/gz/read.rs

@@ -98,7 +98,7 @@ impl<R: Read + Write> Write for GzEncoder<R> {
 /// After reading a single member of the gzip data this reader will return
 /// Ok(0) even if there are more bytes available in the underlying reader.
 /// `GzDecoder` may have read additional bytes past the end of the gzip data.
-/// If you need the following bytes, wrap the `Reader` in a `std::io::BufReader` 
+/// If you need the following bytes, wrap the `Reader` in a `std::io::BufReader`
 /// and use `bufread::GzDecoder` instead.
 ///
 /// To handle gzip files that may have multiple members, see [`MultiGzDecoder`]

src/gz/write.rs

@@ -171,8 +171,8 @@ impl<W: Write> Drop for GzEncoder<W> {
 /// This structure exposes a [`Write`] interface, receiving compressed data and
 /// writing uncompressed data to the underlying writer.
 ///
-/// After decoding a single member of the gzip data this writer will return the number of bytes up to 
-/// to the end of the gzip member and subsequent writes will return Ok(0) allowing the caller to 
+/// After decoding a single member of the gzip data this writer will return the number of bytes up to
+/// to the end of the gzip member and subsequent writes will return Ok(0) allowing the caller to
 /// handle any data following the gzip member.
 ///
 /// To handle gzip files that may have multiple members, see [`MultiGzDecoder`]

src/lib.rs

@@ -70,8 +70,8 @@
 //! While most `gzip` files one encounters will have a single *member* that can be read
 //! with the [`GzDecoder`], there may be some files which have multiple members.
 //!
-//! A [`GzDecoder`] will only read the first member of gzip data, which may unexpectedly 
-//! provide partial results when a multi-member gzip file is encountered. `GzDecoder` is appropriate 
+//! A [`GzDecoder`] will only read the first member of gzip data, which may unexpectedly
+//! provide partial results when a multi-member gzip file is encountered. `GzDecoder` is appropriate
 //! for data that is designed to be read as single members from a multi-member file. `bufread::GzDecoder`
 //! and `write::GzDecoder` also allow non-gzip data following gzip data to be handled.
 //!
@@ -81,11 +81,6 @@
 //! emit an error after decoding the gzip data. This behavior matches the `gzip`,
 //! `gunzip`, and `zcat` command line tools.
 //!
-//! Chrome and Firefox appear to implement behavior like `GzDecoder`, ignoring data
-//! after the first member. `curl` appears to implement behavior somewhat like
-//! `GzDecoder`, only decoding the first member, but emitting an error if there is
-//! data after the first member, whether or not it is gzip data.
-//!
 //! [`read`]: read/index.html
 //! [`bufread`]: bufread/index.html
 //! [`write`]: write/index.html