diff --git a/README.txt b/README.txt
index dfc8f81..c18fb82 100644
--- a/README.txt
+++ b/README.txt
@@ -1,7 +1,15 @@
+                     ____                 \
+   ____ ______      / __/___  ____     \   \
+  / __ `/ ___/_____/ /_/ __ \/ __ \  \  |   |
+ / /_/ / /  /_____/ __/ /_/ / /_/ /  /  |   |
+ \__, /_/        /_/  \____/\____/     /   /
+/____/                                    /
+
+
 Hi!
 
 This is a collection of custom blocks that are not directly associated with a
-special project. For sample applications see:
+project. For sample applications see:
 
 https://github.com/bastibl/gr-ieee802-11
 https://github.com/bastibl/gr-ieee802-15-4
@@ -10,19 +18,20 @@ https://github.com/bastibl/gr-ieee802-15-4
 
 ### Wireshark Connector
 
-This blocks outputs PDUs in the PCAP format. The resulting file can be opened in
-nearly all network monitoring applications. Some examples are Wireshark, Tshark,
-and tcpdump. Currently, it support WiFi packets with radiotap header and ZigBee.
+This blocks outputs PDUs in the PCAP format which is supported by all common
+network monitoring applications. Some examples are Wireshark, Tshark, and
+tcpdump. Currently, it supports WiFi packets with Radiotap header and ZigBee.
 
-Since GNU Radio does not support File Sinks that append to a file, one can not
-open Linux pipes / fifos. For that reason, it is not easily possible to monitor
-traffic live. However, loading the file in Wireshark works.
+Since GNU Radio File Sinks have hard-coded open flags that include O_TRUNC one
+can not open Linux pipes. For that reason, it is not possible to monitor traffic
+live by connection Wireshark to a pipe. However, opening the file and
+investigating the traffic offline works fine.
 
-I made a patch that adds an append option to the File Sink. If you are
-interested see:
-https://github.com/bastibl/gnuradio/commit/befa5bd94b59a56e13d7ec4fe0da86637fe624d9
+I made a patch that adds an append option to the File Sink. With this patch you
+can also open pipes. If you are interested see:
+https://github.com/bastibl/gnuradio/
 
-For further information about radiotap, pcap, and Wireshark see:
+For further information about Radiotap, PCAP, and Wireshark see:
 http://www.radiotap.org/
 http://www.wireshark.org/
 
@@ -30,9 +39,10 @@ http://www.wireshark.org/
 
 ### Burst Tagger
 
-Tags a burst / packet with tx_sob und tx_eob tags. This is useful if the SDR is
-operating in half duplex mode. With adding a tx_eob the USRP switches back to
-receive mode immediately. That way, direct responses like ACKs are not missed.
+Tags a burst / packet / bunch of samples with tx_sob und tx_eob tags. This is
+useful if the SDR is operating in half-duplex mode. With adding a tx_eob the
+USRP switches back to receive mode immediately. That way, direct responses like
+ACKs are not missed.
 
 The block searches for a special tag that indicates the start of a burst. The
 name of this tag is configurable. The tag should indicate the length of the
@@ -51,19 +61,19 @@ like ACKs, retransmission and stuff.
 ### Packet Pad
 
 Adds a configurable number of zeros before and after a burst. The burst has to
-be started with an tx_sob, and ended with a tx_eob tag.
-From time to time I had issues when I did not pad the sample stream. This block
-helps to investigate that.
-Also it is handy for loopback testing when there is no continues sample stream.
+be started with an tx_sob, and ended with a tx_eob tag. From time to time I had
+issues when I did not pad the sample stream. This block helps to investigate
+that. It is also handy for loopback testing when there is no continues sample
+stream.
 
 
 
 ### Periodic Msg Source
 
-This block sends messages at regular intervals  much like the message strobe block in
-mainline GNU Radio. With this block you can in addition configure the number of
-packets that are sent. When all normal messages are sent, the blocks sends a final
-PMT_EOF message to indicate that it is done.
+This block sends messages at regular intervals much like the Message Strobe
+block in mainline GNU Radio. With this block you can also configure the number
+of packets that are sent. When all normal messages are sent, the blocks sends a
+final PMT_EOF message to indicate that it is done.
 I used this block for automated performance tests with no-GUI flow graphs.